[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[coldsync-hackers] Am I on the right track?
- To: coldsync-hackers at lusars dot net
- Subject: [coldsync-hackers] Am I on the right track?
- From: Dave Hall <dave dot hall at mbox.com.au>
- Date: Sun, 29 Dec 2002 17:45:39 +1100
- Reply-to: coldsync-hackers at lusars dot net
- Resent-date: Wed, 22 Jan 2003 20:47:07 -0800
- Resent-from: jferg at newshell dot lusars.net
- Resent-message-id: <200301230447.h0N4l7GU031965@shell.lusars.net>
- Resent-to: coldsync-hackers-archive at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
Hi all,
I have spent some time reading your docs. I am impressed with what i
have seen so far - keep up the great work :)
I am currently reworking the phpgroupware conduits and axissync to do
full two way syncing between palms and phpgroupware/axisgroupware.
I want coldsync to use a common/generic config and conduits. I was
hoping that someone here could confirm that i am on the right track.
Here is what i plan to do:
* add the appropriate line/s to my /etc/services and inetd.conf - as in
the README.daemon file, but with a -f
/usr/local/etc/allusers-coldsync.rc and a group in inetd.conf so php can
modify the etc/palms file and coldsync can still read it.
* use a /usr/local/etc/allusers-coldsync.rc file similar to this
########################################
### Options block
########################################
# I don't think i need anything here
########################################
### Listen block
########################################
listen serial "netsync-inetd" {
protocol: net;
device: stdin;
noprompt;
}
########################################
### Conduits
########################################
## Generic - Needed??
conduit sync {
path: [generic];
type: */*;
default;
}
## Memos <-> Notes
conduit fetch, dump {
path: "/path/to/phpgroupware/palmsync/conduits/phpgw_memos";
type: memo/DATA;
}
## DateBook <-> Calendar
conduit fetch, dump {
path: "/path/to/phpgroupware/palmsync/conduits/phpgw_datebook";
type: date/DATA;
}
## ToDo <-> ToDo
conduit fetch, dump {
path: "/path/to/phpgroupware/palmsync/conduits/todo_datebook";
type: todo/DATA;
}
## Addressbook <-> Contacts
conduit fetch, dump {
path: "/path/to/phpgroupware/palmsync/conduits/todo_addressbook";
type: addr/DATA;
}
* I plan to have a /usr/local/etc/palms like so:
########################################
### Palm List
########################################
pda "user1 Palm" {
snum: "S0M3SER1ALH3R-E";
username: "user1 real name";
directory: "/path/to/phpgroupware-vfs/user1/palm";
}
pda "user2 Palm" {
snum: "4N0TH3RSER1AL-0";
username: "user2 real name";
directory: "/path/to/phpgroupware-vfs/user2/palm";
}
I have a few questions also :)
Is it possible to get the palm username and serial number for use in the
conduits? I need this info to authenticate the real user on phpgroupware.
Is it still the case that P5-Palm/coldsync can read categories from the
palm but not edit/add them?
I am using 3.0-pre3 and will be recommending others use this (or the
final release) for the conduits i write.
Thanks in advance.
Cheers
Dave Hall (aka skwashd)
begin:vcard
n:Hall;Dave
fn:Dave Hall
tel;fax:+61 3 8610 0029
tel;work:+61 3 96 871 871
org:Dave Hall Consulting;
adr:;;;;;;AUSTRALIA
version:2.1
email;internet:dave.hall@mbox.com.au
end:vcard