Re: GUPnP device description handling

Hi all,

In our application, we initially have just the template for the file
on the filesystem.
Then we load the template and fill friendly name, udn, etc.
At the end we serialize the content into a temporary file to match the
current API.

It is no big deal to create the temporary file.
But I don't agree that the file is (always) available.

Kind regards

>> Why doesn't it server the xmlDoc directly?
> I don't know/remember the exact reasons Jorn designed it this way but
> the XML doc can't just be served as is but needs to be serialized.
> Don't really think thats an issue in home network but could be a big
> performance issue in corporate networks (not the main target audience
> though) so why not send the original file as is since its available?
> --
> Regards,
> Zeeshan Ali (Khattak)
> FSF member#5124
> ------------------------------
> _______________________________________________
> gupnp-list mailing list
> gupnp-list gnome org
> End of gupnp-list Digest, Vol 14, Issue 5
> *****************************************

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]