Re: [coldsync-hackers] plugins (dynamic library) and search paths.

[Fred Gylys-Colwell <fredgc@ktb.net>]

On Thu, Aug 16, 2001 at 10:38:00PM -0400, Andrew Arensburger wrote:
> On Thu, 16 Aug 2001, Fred Gylys-Colwell wrote:
> > search paths:  I would like to have the .coldsyncrc file have a "search path"
...
> 	In any case, if I were doing it right now, I'd probably have the
> parser create a linked list, put it in the configuration struct, and allow
> run_conduit() to look at the list. If you want to do something like this,
> go for it.

O.K.  I'll play around with it.


> 
> > plugins:  I have added a routine that loads a library (using dlopen etc.) so
....
> 	I originally conceived of conduits as being dlopen()able shared
> libraries, but eventually decided to have them run as separate processes.
> That way, if a conduit dumps core, it doesn't bring down the entire
> application with it. Also, an external conduit can be setuid without
> requiring the entire application to be setuid. 

I agree about the core dumps, and I hadn't even thought about the other stuff.
I think I better back of on shared libraries for now.

...
> 
> 	Sync conduits can use SPC. This is basically a DLP request with a
> header in front. 

Maybe I should look at this some more.  It might be easier to make this what I
want.  Perhaps there could be a dummy PConnection that just wraps up its DLP
requests and sends them to coldsync?  Then I could use DlpOpenDB from
libpconn. 

-- Fred.


-- 
----------------------------------------------------------------------
	    Fred Gylys-Colwell      fredgc@member.ams.org
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.