[OGo-Evolution] working mangling daemon allowing basic OGo-Evolution

[Helge Hess]

On Oct 21, 2004, at 10:52, Erik Romijn wrote:
> With a PROPPATCH ZideStore returns a HTTP501 (method not implemented). 
> I
> thought that meant that the request was not supported.

Yes, I suppose this would be correct HTTP ;-)

ZideStore currently returns 501 whenever it encounters a requests which 
it basically understands but can't handle. If there is a better 
response code for this case, let me know.

> If ZideStore already supports the PROPPATCH we would just have to find
> out what exactly has changed that makes ZideStore return a 501.

Exactly.

BTW: Actually what URL supports what request is determined by the so 
called "SoObjects" (which are bound to the URL lookup path and can be 
found in ZideStore/SoObjects/ in the source). So while a 
SoContactFolder might support PROPPATCH this doesn't imply that a 
SoCalendarFolder does as well.
Those folders (and contained objects) are responsible for mapping some 
form of HTTP data to the internal OGo Logic calls.

> An addition to the PUT's on calendar items: Evo returns an error after
> PUTting the item although it is added correctly. Probably ZideStore's
> response would have to be modified to make Evo believe it was 
> succesful.

What does it return at the moment? If its 200 (Ok), one might try 201 
(Created).

Greets,
   Helge
-- 
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org