[OGo-Evolution] Re: Evo 2.0

[Helge Hess]

Hi Erik,

moved discussion to evolution list, might be interesting for other 
people ;-)

On Oct 19, 2004, at 15:47, Erik Romijn wrote:
> The current way tasks are implemented is: fetch the names from the
> PROPFIND and do a GET on each task item.

The Connector accesses Exchange that way? (its not an OGo issue, 
right?) Maybe Dan can explain why no BPROPFIND is used for tasks.

What does the GET return? I suppose an iCal VTODO wrapped in a MIME 
message?

> This is done because we could
> not find a way to make zidestore return all the needed data for all the
> tasks in a single request.

I could probably create a method which returns all tasks in a single 
call. What format would you prefer?

> Ofcourse this is very ugly and very slow.
> The slowness can be 'prevented' with a caching system.

Yes, the caching system is a good idea in any way, but as mentioned it 
really belongs into the Connector ;-)

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