<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2657.73">
<TITLE>RE: [mythtv] MythSOAP Expressions Of Interest</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Good points. I'd love to hear your thoughts in regards to these issues as I'm still lacking in knowledge.</FONT>
</P>
<P><FONT SIZE=2>>>this would move to _requiring_ the backend to be running</FONT>
<BR><FONT SIZE=2>Would that be only if they wanted to use the integration (SOAP) layer, or all the time?</FONT>
</P>
<P><FONT SIZE=2>>>my concern is that SOAP (like anything using XML) adds a lot of </FONT>
<BR><FONT SIZE=2>>>size + parsing complexity</FONT>
</P>
<P><FONT SIZE=2>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).</FONT></P>
<P><FONT SIZE=2>With respect to size, are you talking memory footprint or actual deployment size? Would making it an optional module would help here?</FONT></P>
<BR>
<BR>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: mythtv-dev-bounces@mythtv.org</FONT>
<BR><FONT SIZE=2>[<A HREF="mailto:mythtv-dev-bounces@mythtv.org">mailto:mythtv-dev-bounces@mythtv.org</A>]On Behalf Of Isaac Richards</FONT>
<BR><FONT SIZE=2>Sent: Monday, February 21, 2005 1:22 PM</FONT>
<BR><FONT SIZE=2>To: Development of mythtv</FONT>
<BR><FONT SIZE=2>Subject: Re: [mythtv] MythSOAP Expressions Of Interest</FONT>
</P>
<BR>
<P><FONT SIZE=2>On Sunday 20 February 2005 06:52 pm, Kevin Kuphal wrote:</FONT>
<BR><FONT SIZE=2>> bill peck wrote:</FONT>
<BR><FONT SIZE=2>> >While I do think SOAP would be handy I would settle for program guide</FONT>
<BR><FONT SIZE=2>> >data being available over the current Myth Protocol instead of having</FONT>
<BR><FONT SIZE=2>> >to do SQL calls.</FONT>
<BR><FONT SIZE=2>></FONT>
<BR><FONT SIZE=2>> This type of increased independence of the frontend was something I had</FONT>
<BR><FONT SIZE=2>> mentioned to Isaac as a point of interest to me. Not specifically for</FONT>
<BR><FONT SIZE=2>> SOAP, but having more functions in the protocol would lend itself to</FONT>
<BR><FONT SIZE=2>> improving such an effort just as it could have a positive effect on the</FONT>
<BR><FONT SIZE=2>> MediaMVP work, etc. He wasn't against it but noted that currently only</FONT>
<BR><FONT SIZE=2>> the functions required to be done on the backend are done there. Not</FONT>
<BR><FONT SIZE=2>> sure when I might have time to visit this, but it is something I'd like</FONT>
<BR><FONT SIZE=2>> to work on as well.</FONT>
</P>
<P><FONT SIZE=2>Right - this would move to _requiring_ the backend to be running for </FONT>
<BR><FONT SIZE=2>everything. It's not now, and I don't know if I'm happy with that additional </FONT>
<BR><FONT SIZE=2>requirement.</FONT>
</P>
<P><FONT SIZE=2>Additionally, my concern is that SOAP (like anything using XML) adds a lot of </FONT>
<BR><FONT SIZE=2>size + parsing complexity to what needs to be a lightweight system if it's </FONT>
<BR><FONT SIZE=2>going to be used for all message passing between processes. </FONT>
</P>
<P><FONT SIZE=2>Isaac</FONT>
<BR><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>mythtv-dev mailing list</FONT>
<BR><FONT SIZE=2>mythtv-dev@mythtv.org</FONT>
<BR><FONT SIZE=2><A HREF="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev" TARGET="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev</A></FONT>
</P>
</BODY>
<!--[object_id=#infocomp.com#]--><P><FONT face=Arial color=#808080 size=1>Important notice: This message is intended for the individual(s) and entity(s) addressed. The information contained in this transmission and any attached, may be confidential and may also be the subject of legal privilege, public interest immunity or legal professional privilege. Any review, retransmission, dissemination or other use of, taking of any action in reliance upon this information by person or entities other than the recipient is prohibited and requires authorization from the sender. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person) you may not copy or deliver this message to anyone. In such cases you should destroy this message and kindly notify the sender by reply email. </FONT></P>
<P><FONT face=Arial color=#808080 size=1>WARNING: Although Infocomp has taken reasonable precautions so that no viruses are present in this e-mail, the company cannot accept responsibility for any loss or damage arising from the use of e-mail attachments.</FONT></P></HTML>