Isaac Richards wrote:
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.
You don't need the backend running for just about everything right now?
There might be some tools that don't need a connection to the backend
but as far as I see it they could still continue to do so, access to the
database server would not be prevented. But it would give other frontend
applications a way to get at all the possible information using a single
point-of-entry.
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.
I tend to agree with you here. I myself have been looking for some time
now at the DBus project (http://freedesktop.org/wiki/Software_2fdbus)
which is a very light-weight IPC message bus. The problem so far has
been the lack of finished QT bindings.
-Tako
_______________________________________________
mythtv-dev mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
