On Thu, 3 Jan 2002 13:50:16 +0100
Tom <tom_at_lemuria.org> wrote:
> On Thu, Jan 03, 2002 at 12:44:36PM +0100, Nils Faerber wrote:
> > > > I had a dig. Its under a BSD license because you have to license
> > > > patents to implement syncml and do so under as yet undecided
> terms.
> > > That is unfortunate. The "SyncML Intellectual Property/Patent
> Issues"
> > It is, indeed.
> > What are "open" standards good for if they cannot be used real _open_
> > (i.e. freely)?
> well, syncml is only a few months old and the first software using it
> is just appearing. I wouldn't necessarily say it's an established
> standard, yet.
But they aim at beeing "the" standard :(
This is basically a good idea but not beeing real open (i.e. free) means a
no-go for many possible applications especially open source applications.
Maybe they could be talked into something that it can be freely used in
non-profit applications.
> > > for Linux then so be it, I'll try.
> > > Anybody have an idea how we can solve the synchronization problem?
> > Some use rsync, like the Agenda VR3.
> > But this has new side effects.
> if we agree to use an SQL backend, then db dumps in SQL format seem to
> be the most portable way to go and are fully rsync compatabile. as an
> alternative, we could sync the transaction logs or go with timestamps
> (select * from addresses where last_update > X).
Wouldn't dumps imply that you first have to do the dump into some local
file before you can rsync it?
When we think about really huge databases that do not fit into the loca
RAM we get a problem. RSyncing the raw database would be better here.
Maybe we should ask the SQLite author in making the file format
portable... (if it isn't already ;)
CU
nils faerber
-- kernel concepts Tel: +49-271-771091-12 Dreisbachstr. 24 Fax: +49-271-771091-19 D-57250 Netphen D1 : +49-170-2729106 --Received on Thu Jan 03 2002 - 05:41:59 EST
This archive was generated by hypermail 2.2.0 : Mon Jul 25 2005 - 17:18:59 EDT