Re: XML-RPC on an embedded device?

For embedded application I suggest c rather than java.
Expat  (SAX style) XML parser is highly efficient and
portable even for embedded applications.
regards
Sudhakar

 --- Paul Libbrecht <paul@xxxxxxxxxxxxxx> wrote: 
> 
> 
> I think that, in the java world, this was the intent
> of the authors of 
> the MinML parser, a quite minimal parser that is
> suitable for XML-RPC. 
> Have you checked their web-page ?
> 
> Do note that if you have a bit of time (three days
> at most of 
> development maybe ?), writing a dedicated parser for
> XML-RPC is easy 
> and can be super efficient, I believe. For example,
> there's very little 
> attributes in XML-RPC...
> 
> paul
> 
> 
> Le 17 nov. 04, à 22:15, jesseema a écrit :
> > Hi, I'm new to XML-RPC and am considering it for
> use in an
> > application that controls and monitors an embedded
> device.  The
> > device is running embedded Linux and the software
> is written in C++.
> > The software architecture is based on several
> daemon processes that
> > communicate amongst themselves using a
> publish/subscribe model (i.e.
> > subject/observer).  For example, one of the
> processes monitors a
> > sensor and sends a notification message to all
> subscribers when
> > certain conditions are met.  The embedded device
> is externally
> > monitored using a Windows-based operator terminal.
>  The current
> > design uses a custom IPC protocol over sockets
> that is somewhat
> > difficult to use.
> >
> > I've only recently discovered XML-RPC and am
> wondering if it would
> > work well for our inter-process communication. 
> I'm already
> > considering replacing the current IPC mechanism
> with a XML message
> > passing scheme, so maybe I could go one step
> further and use XML-
> > RPC.  Does XML-RPC work well with a
> publish-subscribe model rather
> > than a strict client-server model?  I would assume
> that both the
> > publisher process and the subscriber process would
> have to act as
> > both a client and server for XML-RPC.  I'm also
> concerned about the
> > added overhead of requiring an HTTP server in
> every process.
> >
> > Is anyone else doing this sort of thing with
> XML-RPC?  Is this an
> > appropriate way to use it?  Any thoughts/comments
> are much
> > appreciated.
> >
> > Thanks,
> > Mark
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
> 
> 
> 
> 
> 
> 
>  
> Yahoo! Groups Links
> 
> 
>     xml-rpc-unsubscribe@xxxxxxxxxxxxxxx
> 
>  
> 
> 
> 
>  

________________________________________________________________________
Yahoo! India Matrimony: Find your life partner online
Go to: http://yahoo.shaadi.com/india-matrimony


 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/xml-rpc/

<*> To unsubscribe from this group, send an email to:
    xml-rpc-unsubscribe@xxxxxxxxxxxxxxx

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/