[GroupDAV] Synclet-type converters for various GroupDAV servers?

[Mathew McBride]

This is one of the reasons I designed the processing module to be
user-extensible, breaking out the data conversion for different servers can
be done in the same way. I might move the part of the processing module tha=
t
calls the converters into a separate, overridable function. One could then
just copy funambol2ical4j/ical4j2funambol into their own class and customiz=
e
what happens. =20

At the moment 'customizing' the processing module requires one to create a
Funambol module and a XML-serialized bean*, like what Funambol already does
for just about everything. BeanShell was definitely on my mind at the time,
and the glue to do this will come sometime soon.

(*or modify the connector like I did with S60 todo sync last week)
On 27/2/08 2:17 AM, "Samuli Sepp=E4nen" <samuli.seppanen@tietoteema.fi> wrote=
:

>=20
> Now to the actual idea... How difficult would it be to create separate
> (VCALENDAR) converter classes for each backend server? Or implement the
> same code with Beanshell, like with Funambol synclets? User could then
> select server type (OGo 1.0/OGo 1.1.x/Citadel...) and the appropriate
> converter code would then be used automatically. GroupDAV connector's
> core code wouldn't then have to touch VCALENDAR content at all -
> everything would be handled by the server-specific code.
>=20
> This would make it much easier to integrate the GroupDAV connector with
> various backend servers - especially if the server-specific code was in
> Beanshell (=3Dno need to compile the GroupDAV connector code).
>=20
> Please tell me what you think.
>=20
> Samuli