Hey Jorn!
Most of the functionality of gupnp-universal-cp is already
implemented. The functions remaining are:
1. Method Invocation
2. Divide the code into more than one file (it's already >1200 LOC and
88 functions).
3. Adding a device manually: User could provide us with Location and
we create the proxies from that.
The first two only needs to be done by i wonder if #3 is possible
with the current API. If it is not, would you want to support that or
you think this is also something only this particular app would need?
I think this feature would be needed by us (Nokia) when/if we port our
clinkc-based code to gupnp. As you probably already know, we launch
the stream-engine each time the user makes a call and there is no time
to discover internet-gw device just to open the port. The solution we
have figured is a local discovery caching daemon, so the discovery and
control are in separate processes.
Do you think I should start sending you the patches already or
wait till the completion of the app? Also would mind the unix name to
be 'guniversal-cp' instead? Not only is the name more shorter and sexy
but also that I thinking of writing a console-based version as well so
the binaries would be named 'guniversal-cp' and 'guniversal-cp-gui'
('gunp-universal-cp-gui' looks too long and ugly). What do you think?
P.S Normally i wouldn't be asking you about things likes names but
this app is going into gupnp, so your approval is a must. :)
-- Regards, Zeeshan Ali FSF member#5124 -- To unsubscribe send a mail to gupnp+unsubscribe\@o-hand.comReceived on Wed, 1 Aug 2007 18:46:13 +0300
This archive was generated by hypermail 2.1.8 : Wed Aug 01 2007 - 12:00:06 EDT