[mythtv] MythSOAP Expressions Of Interest

[Adam Jenkins]

Good points.  I'd love to hear your thoughts in regards to these issues as
I'm still lacking in knowledge.

>>this would move to _requiring_ the backend to be running
Would that be only if they wanted to use the integration (SOAP) layer, or
all the time?

>>my concern is that SOAP (like anything using XML) adds a lot of 
>>size + parsing complexity

In regards to parsing complexity, do you mean development or during runtime?
As most SOAP binding systems these days are designed to be reasonably
transparent to the implementing system, development time is relatively
trivial (just supply a WSDL file and binding points).  In regards to runtime
parsing, the soap toolkit from apache has acheived some really good
benchmarks (they've upgrade to SAX).

With respect to size, are you talking memory footprint or actual deployment
size?  Would making it an optional module would help here?



-----Original Message-----
From: mythtv-dev-bounces at mythtv.org
[mailto:mythtv-dev-bounces at mythtv.org]On Behalf Of Isaac Richards
Sent: Monday, February 21, 2005 1:22 PM
To: Development of mythtv
Subject: Re: [mythtv] MythSOAP Expressions Of Interest


On Sunday 20 February 2005 06:52 pm, Kevin Kuphal wrote:
> bill peck wrote:
> >While I do think SOAP would be handy I would settle for program guide
> >data being available over the current Myth Protocol instead of having
> >to do SQL calls.
>
> This type of increased independence of the frontend was something I had
> mentioned to Isaac as a point of interest to me.  Not specifically for
> SOAP, but having more functions in the protocol would lend itself to
> improving such an effort just as it could have a positive effect on the
> MediaMVP work, etc.  He wasn't against it but noted that currently only
> the functions required to be done on the backend are done there.  Not
> sure when I might have time to visit this, but it is something I'd like
> to work on as well.

Right - this would move to _requiring_ the backend to be running for 
everything.  It's not now, and I don't know if I'm happy with that
additional 
requirement.

Additionally, my concern is that SOAP (like anything using XML) adds a lot
of 
size + parsing complexity to what needs to be a lightweight system if it's 
going to be used for all message passing between processes.  

Isaac
_______________________________________________
mythtv-dev mailing list
mythtv-dev at mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-dev/attachments/20050221/0fe84140/attachment.htm