Re: [coldsync-hackers] Hotsync proxy to coldsync ...

[Johan Van den Brande <johan@vandenbrande.com>]

Hi,

> > I'm using coldsync in a networked environment, i.e. doing a network sync
> > to coldsync
> > from a windows (sorry) PC.
> 
>         Are you actually doing this, or are you just hypothesizing? If
> the former, then I'd be interested in hearing how well it works. I
> have a shortage of Windows machines to test with.

It works! I did not get the inetd stuff to work *yet*, but I start up
the
coldsync by hand on the linux box and then press the hotsync button on
my Palm connected to my w2k machine ... and it does the stuff!

> > Now, I was thinking about a sort of hotsync proxy that redirects the
> > sync of one database to
> > a networked coldsync linux, all the other databases are synced to local
> > conduits...


> But if you're going to be doing that anyway, why not keep your life
> simple and write a conduit that Does The Right Thing in the first
> place? That is, if you want to sync your Address Book with the
> corporate LDAP server, don't forward it to ColdSync on a remote
> machine, talk to the LDAP server directly.
> 
>         Sorry I couldn't give you a better answer.

The deeper motiviation for this to happen is to write an OSS sync
server, like
the Hotsync server from Palm. What I want to limit is the need to
completely
rewrite conduits on the server side. There are already usefull Palm::PDB
codecs
for Memo, Doc, Timesheet ( ;-) ) ... etc ... 

Another route I'm thinkering about is using a generic hotsync conduit
that forwards
the PDB structure (categories etc ...) via a protocol ( probably XML-RPC
over HTTP)
to a server application that reconstructs the behaviour of COldsync, ie
to keep the
conduits compatible ... I'm thinking about using apache as a middle-ware
core (message
broker ) and writing it in the mod_perl framework .. ie a sort of
mod_palmsync kind
of thingy. This would lower my investment in time, as I can recup the
p5-Palm modules and
a lot of coldsync conduits. Also apache and mod_perl together with the
XMLRPC::Lite or Frontier::XMLRPC
modules would give me a head start. I've *some* experience in writing
hotsync conduits in Java.

This is all just in the concept phase, as I've no time left for the
moment to start this
project. I first need to finish some other stuff.

Do you know of any GUI projects for coldsync? They all seem to be build
arounf pilot-link, but
pilot-link is a bit archaic IMHO ...

Johan
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.