RE: [Phpgroupware-developers] Palm sync conduits for phpgw

[Brian Johnson]

I chose Coldsync because there was a already a conduit that claimed that it
synced to the phpgw datebook (I haven't been able to get it to work)

However, there are other reasons why I stuck to Coldsync:
1. it to allows conduits to be written in perl (that's what I'm doing) - but
it also allows other languages
2. it allows Palm syncing without the user having to log in first (ie. walk
up, stick the Palm in the cradle, hit the hardware hotsync button, and walk
away)
3. it allows network hotsyncing from Linux or Windows computers (again
without having to log in first)
4. it splits up the synchronization process so that any server modification
of the data can be performed after the user has picked up the Palm (this
means faster syncing since the Palm doesn't sit there waiting for the host
computer to do other stuff)
5. there is an operational Coldsync conduit that gets data from the
Timesheet program from the Palm and creates invoices in MS Excel with the
data (I intend to modify this to sync with the timetrack module in phpgw)

Why I didn't use XMLRPC
1. I didn't know it existed for phpgw
2. when I started, it wasn't operational
3. any updates to phpgw will require updates to XMLRPC before the conduits
work again (this is true for using SQL directly as well, however, I can
debug SQL and since I'm not a programmer, I don't want to learn XMLRPC.
Also, I can debug SQL - I don't have to wait for anyone else)
4. any interface that I've had experience with has limitations, I doubt
XMLRPC will return the info that I'm looking for in the format the I need it
(I know this is quite the assumption, but before you judge me, look at the
SQL queries I'm using and tell me that they are EASILY implementable through
XMLRPC)
5. someone else can learn that interface and if it's as easy as claimed, it
should be a simple matter of replacing my SQL queries





-----Original Message-----
From: address@hidden
[mailto:address@hidden Behalf Of Jean-Eric
Cuendet
Sent: Thursday, April 11, 2002 4:45 AM
To: address@hidden
Subject: Re: [Phpgroupware-developers] Palm sync conduits for phpgw


Have you tried PilotManager? A manager of syncing in Perl with Tk interface.
You would just have to create a conduit using XMLRPC/SOAP/SyncML to made
it do the job!
-jec

Brian Johnson wrote:

>I've been working on conduits to sync phpgw and I have one working for the
>memo/notes module
>
>However, currently it justs syncs records made by the user doing the
syncing
>and I would like to expand it to support the phpgw access rights system
>
>My conduit is in Perl and I am using SQL statements to access the phpgw
>database
>
>I have had trouble determining how the tables/fields interact to determine
>what access the current user has to each record
>
>Can someone explain it to me?
>
>
>_______________________________________________
>Phpgroupware-developers mailing list
>address@hidden
>http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
>

--
Jean-Eric Cuendet
Linkvest SA
Av des Baumettes 19, 1020 Renens Switzerland
Tel +41 21 632 9043  Fax +41 21 632 9090
E-mail: address@hidden
http://www.linkvest.com
--------------------------------------------------------




_______________________________________________
Phpgroupware-developers mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/phpgroupware-developers