[Kolab-devel] removal of legacy ftp support

[Stephan Buys]

No,no,no,no,no please!

Legacy clients use ftp upload. This is of special importance for clients who
do not use Toltec (and do not have server-side Calendars) and other legacy
Toltec clients. Outlook 2000 is a good example, but I am sure there are other
calendaring apps out there as well.

It works very elegantly with ftp uploading the F/B lists directly into the freebusy.php
scripts' cache folder and only adds capabilities to the clients. An assertion 
that we dont need to upload anymore is only true for a handfull of email clients.

So I definitely oppose the suggestion, lets not remove functionality that some
people are definitely still using today.

Kind regards,
Stephan



On Sunday 03 October 2004 05:24, Martin Konold wrote:
> 
> Hi,
> 
> I am considering to remove the ftp capability from Kolab 2.
> 
> From a security point of view ftp was always a nightmare and I think that 
> neither the ftp upload nor download features are required anymore.
> 
> On one hand we will gain server generated free-busy lists with Kolab 2 and on 
> the other we can use https and webdav as communication protocols for both 
> uploads and downloads.
> 
> Opinions welcome!
> 
> Yours,
> -- martin
> 
> "I am committed to helping Ohio deliver its electoral votes to the
> President next year."
>   -- Wally O'Dell - CEO of Diebold, Inc. (One of the largest American
>   manufacturers of election machinery)
> 
> e r f r a k o n
> Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
> 
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailmanlistinfo/kolab-devel
> 
> 
> 

-- 
Stephan  Buys
Code Fusion cc.
Tel: +27 11 673 0411
Mobile: +27 83 294 1876
Email: s.buys at codefusion.co.za

E-mail Solutions, Kolab Specialists.
http://www.codefusion.co.za