[Kolab-devel] Kolab2 architecture/format flaws

[Matt Douhan]

On Friday 13 May 2005 16.41, Zachariah Mully wrote:
>
> I understand that this is part of your contract, and I am very
> appreciative of the work and code that you've contributed to the
> community... but this is extremely shortsighted. You've limited yourself
> to desktop only deployments, and offered nobody a means to access their
> data from an web terminal somewhere on the road. Most the salespeople I
> work with, make heavy use of public terminals to check mail through our
> webinterface as it's far more convenient and faster to sit down, login,
> check and leave, than it is to fish their laptop out, plug it in, find a
> network to connect to ....
>
> So I suppose what I'm worried about is that this design decision
> severely hinders the development of any viable webclient, or any other
> thin clients (mobile devices, for instance, no eff'in way I'm syncing
> the entire calendar store over a GPRS connection), and it has no bearing
> on the development or design decisions of fat clients. You're still free
> to use disk caches, but you open up a whole host of server-side
> optimizations for thin clients.
>

Although the issues brought up here are real, it is also fair to say that we 
are curently running a multithousand user installation with Kolab2 Beta5, 
including Horde and not a single support call ( I just checked ) has been 
logged due to slow performance of the web client.

rgds

Matt

-- 
Matt Douhan
www.fruitsalad.org
kolab + toltec + horde + kontact == success