[coherence-dev] would be better if there is a default conf file under ~/

[jean-michel Sizun]

Hi,

At first, thanks for trying Coherence.
my so-called answers in your mail.
regards,
Jean-Michel

2009/10/29 simon <Yuntong.Jin at sun.com>

> Hi list,
>   I could find it anywhere, would be better if  there is a default conf
> file under ~/, so user can just set active=yes instead of write down some
> thing like
> <plugin active="yes">
>  <backend>YouTubeStore</backend>
>  <name>YouTube</name>
> </plugin>
>

The framework is meant to be a developpement framework to support any kind
of UPnP device.
It is easy to use it to power a media server by activating the store
backends but it is only one goal among several.
As a result, the configuration file/process is effectively more
developper-friendly than mediaserver-friendly.

If ever you're profficient in python language (or interested in digging some
things up), a good thing would be to develop a layer above the framework +
backends to get a more mediaserver-specific configuration process.

Anyway, there are some work underway to design a configuration IHM for the
backends (check the mailing-list archive).


> Another question about how to enable YouTube backend, i saw wiki
> http://coherence.beebits.net/wiki/YouTube
> Aside of write config file, do i still need add those python and Dbus
> codes?
>

I do not understand your question. What are 'those python and Dbus codes'
you  are reffering to?
Normally, the only additionnal dependency is python-gdata.

how can i run coherence --plugin=backend:YouTube when there is a process
> already running on system :
> /usr/bin/coherence -o use_dbus:yes -o controlpoint:yes
> which is triaged by  //usr/share/dbus-1/services/org.coherence.service/
> automatically
>

I personnally never use the "coherence --plugin=backend:YouTube" syntax but
it may come from trying to reopen a dbus service or to use the same TCP port
(wild guesses).
The best would be for you to open a ticket with the logs of the second
coherence process (the one which fails running).




> BR,
> -Simon
>
> _______________________________________________
> coherence-dev mailing list
> coherence-dev at lists.beebits.net
> http://lists.beebits.net/cgi-bin/mailman/listinfo/coherence-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.beebits.net/pipermail/coherence-dev/attachments/20091112/aab84288/attachment.htm>