[sync] How does rpc work with SyncML

[Anthony Mills]

I think this will work.  The authorizing will be a problem.  SyncML uses 
its own method to authorize.  Could we use some sort of delayed token to 
authorize?  We also need to contend with MD5 username and password, it 
is "required".  But we can get to all that soon enough.  First, I'll 
finish the WBXML stuff, my device only supports that.

Thanks,
Anthony

Chuck Hagenbuch wrote:
> Quoting Anthony Mills <amills at gascard.net>:
> 
> 
>>I have almost finished converting my WBXML stuff to php.  I would like
>>to start adding the SyncML, the last bit to convert depends on which way
>>I go.   How does it work?  The content of the HTTP request goes where?
>>(Let's assume the WBXML is decoded.)  Is a string sent to some other
>>server? a function.  Or is it streamed through the system.  Or are there
>>no plans yet?  The last part assumes the interface is SAX.  I need to
>>change it to fit your design.
> 
> 
> Well, the design is relatively non-existant. So, what do you want to do?
> 
> Right now, the request goes to rpc.php. That page checks the content-type of the
> request and loads the appropriate rpc driver - either the syncml driver
> directly in this case, or an wbxml driver that'll just extend the syncml
> driver.
> 
> It checks authentication, which might have to be tweaked for syncml.
> 
> It grabs the input; it might be better to have an option to just pass in the
> php://stdin stream so that you can use sax on the whole thing.
> 
> Then it calls getResponse() on the rpc driver, and passes the results back to
> the client.
> 
> So there's a lot of flexibility in there.
> 
> -chuck
> 
> --
> Charles Hagenbuch, <chuck at horde.org>
> "I'm really... I'm not too fascinated by green food." - Average Joe
>