[coldsync-hackers] Re: Redux: Netsync + [X]inetd

[Alessandro Zummo <azummo-coldsync2 at towertech dot it>]

 On 01-Mar-02 at 01:16:12,
  Rob Bloodgood <robb@empire2.com> wrote:


> Actually, now that I look at it again before sending, it seems to me that
> any user specific configs (in this "enterprise" setup) can easily be
> handled in .../palms as well:

> NGEVLASI-A|Geeky Doctor|5823|coldsync|/home/coldsync/Geeky
> Doctor/.coldsyncrc

 
It seems we really need something like coldnamed . my suggestion is to write
an abstraction layer which can be used to query the desired backend (ldap,
dns, flat file, db, etc).

It shouldn't be too hard. We may have a structure that describes each
bakend:

struct b
{
    char *name;
    char *description;
  
  .. function pointers ...
}

the backend is responsible to fill the structure with data and function
pointers to a query function, an init one and maybe others....

coldsync will use the one specified with an option directive
and either fallback to a default one or give up with an error if the desired
one doesn't exists. 

It's modular only at compile time but should be ok at most.

Just an idea.. it's quite late and i need some sleep... i'd be happy
to hear comments though.

-- 

  - alex.



-- 
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.