Using libsyncml

[Heikki Lindholm-2]

Hello,

I need to make a syncml engine handling only vcards but being able to
handle many clients at the same time.

I thought I could be using libsyncml. There seems to be parsing
routines, like
smlParserStart
smlParserGetHeader
smlParserGetCommand
smlParserGetStatus

but e.g. details of the elements parsed, like SmlHeader, are hidden in
..._internals.h files and those headers are not installed.

Am I doing something wrong (or just differently from opensync) or have I
missed something?

What would be the correct way to approach the parsing and assembling?

Best regards,
Heikki

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Opensync-users mailing list
Opensync-users@...
https://lists.sourceforge.net/lists/listinfo/opensync-users

[Michael Bell]

Hi Heikki,

Heikki Lindholm wrote:

> I need to make a syncml engine handling only vcards but being able to
> handle many clients at the same time.
>
> I thought I could be using libsyncml. There seems to be parsing
> routines, like
> smlParserStart
> smlParserGetHeader
> smlParserGetCommand
> smlParserGetStatus
>
> but e.g. details of the elements parsed, like SmlHeader, are hidden in
> ..._internals.h files and those headers are not installed.

These functions should not be published. The SyncML protocol stuff is
completely handled by the library. We simply need to reduce our header
files to a minimum. So why do you want to access SyncML directly.

The vcards are only binary blobs for the library. Which must be
encapsulated and send.

> What would be the correct way to approach the parsing and assembling?

This is automatically done by the library. All the transport stuff is
done by libsyncml. SyncML is not fully transparent in terms of the
transport protocol. Therefore we have to implement the XML/WBXML and the
transport specifications.

Best regards

Michael
--
_______________________________________________________________

Michael Bell                    Humboldt-Universitaet zu Berlin

Tel.: [phone]       ZE Computer- und Medienservice
Fax:  [phone]       Unter den Linden 6
michael.bell@...   D-10099 Berlin
_______________________________________________________________

X.509 CA Certificates / Wurzelzertifikate

http://ra.pki.hu-berlin.de


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Opensync-users mailing list
Opensync-users@...
https://lists.sourceforge.net/lists/listinfo/opensync-users

[Heikki Lindholm-2]

Hi Michael,

Thanks for your answer.
Maybe I take a step backwards and explain what I want..

I would like to use apache web server to handle the http transport
(reliability and scalability).
I have a backend DB containing the contact data.
I need to implement apache module to do the syncml engine work.

That module would get the wbxml payload as input, parse it and create
response wbxml and let again the web server to transport it to the client.

... and it would be nice to be able to use libsyncml to do some of the
work...

Best regards,
Heikki

Michael Bell wrote:

> Hi Heikki,
>
> Heikki Lindholm wrote:
>
>> I need to make a syncml engine handling only vcards but being able to
>> handle many clients at the same time.
>>
>> I thought I could be using libsyncml. There seems to be parsing
>> routines, like
>> smlParserStart
>> smlParserGetHeader
>> smlParserGetCommand
>> smlParserGetStatus
>>
>> but e.g. details of the elements parsed, like SmlHeader, are hidden
>> in ..._internals.h files and those headers are not installed.
>
> These functions should not be published. The SyncML protocol stuff is
> completely handled by the library. We simply need to reduce our header
> files to a minimum. So why do you want to access SyncML directly.
>
> The vcards are only binary blobs for the library. Which must be
> encapsulated and send.
>
>> What would be the correct way to approach the parsing and assembling?
>
> This is automatically done by the library. All the transport stuff is
> done by libsyncml. SyncML is not fully transparent in terms of the
> transport protocol. Therefore we have to implement the XML/WBXML and
> the transport specifications.
>
> Best regards
>
> Michael

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Opensync-users mailing list
Opensync-users@...
https://lists.sourceforge.net/lists/listinfo/opensync-users