Re: [Opensync-devel] [RFC] Different libraries for OSYNC_START_TYPE_EXTERNAL

[Henrik /K. <he...@ka...>]

Graham Cobb wrote:
> On Thursday 29 October 2009 15:55:40 Henrik /KaarPoSoft wrote:
>   
>> Daniel Gollub wrote:
>>     
>>> And your real "plugin" which is acutally a complete different process -
>>> or even an own application is implementing a full OSyncClient and
>>> OSyncPlugin environment? Completeyl without that get_sync_info() stuff
>>> ...
>>>       
>> I could do that, but it would take a lot of coding to make my own
>> OSyncClient. That's why I simply use the full opensync library. That's
>> only 10 lines of code!
>>     
>
> I think that is what I have been trying to suggest (badly) -- thanks for the 
> clarification Daniel.
>
> But, of course, Henrik, you shouldn't have to implement your own OSyncClient.  
> What we have to do is to make the client code and plugin support code usable 
> from your process, without bringing in all the rest of OpenSync.  That may be 
> harder than it looks because some functions that plugins call may assume the 
> whole OpenSync environment is present.
>   
Any hints on how to do that would be appreciated!

/Henrik