The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

How to Distribute xPLMediaNet


  • Subject: How to Distribute xPLMediaNet
  • From: "Tony Tofts" <tony@xxxxxxxxxx>
  • Date: Sun, 3 Jul 2005 09:44:53 +0100

Hi All,

Looking for some feedback on how best to distribute xPLMediaNet please?

The version sent to the testers was just a single install with a single
large configuration file containing all existing modules

I'm thinking given the modular nature of xPLMediaNet that it would be
better
to change the way the config file works and make the downloads available
seperately as a pick'n'mix?

I'm thinking of a folder structure along the lines of

<install folder>\xPLMediaNet = core modules
<install folder>\xPLMediaNet\Devices = device modules (e.g. rio,
slimp3,
exstreamer etc)
<install folder>\xPLMediaNet\Sources = source modules (e.g. scanners,
browsers, streams, slimserver, TTS etc)
<install folder>\xPLMediaNet\Transcoders = transcoder modules (e.g.
wav to
mp3 etc)
<install folder>\xPLMediaNet\Interfaces = interface modules (e.g.
web, ppc
etc)
<install folder>\xPLMediaNet\Support = support modules (e.g. dhcp,
tftp etc)

Each subfolder would itself have a number of sub-folders containing the
particular modules dll(s) and config.xml and any other config/program files
required by the module e.g. <install folder>\xPLMediaNet\Devices\Rio

So there would be a standard install package for the core, and then you
would download and dump into an appropriate folder the other modules you
required. I think in the case of a device, like a rio, where there are
other
required modules these should be included in the same download (e.g. rio
would include NFS module, as it's required, but not DHCP which could be
downloaded seperately if required)

The downloads would be a zip file with the contents root in the core folder
(e.g. rio might have .\Devices\Rio\Rio.dll and .\Support\NFS\NFS.dll etc)

This system would be slower to load as the core would need to traverse the
folders looking for modules to load, but I think the advantages would
outway
this?

Also, as people develop their own modules (or modified versions of existing
modules, since source code will be available as separate downloads) these
could easily be added to the site for eveyone to share?

Any thoughts/comments/suggestions please?

Many thanks
Tony



xPL Links: http://www.xplproject.org.uk http://www.xplhal.com http://www.xpl.myby.co.uk
To Post a Message: ukha_xpl@xxxxxxx
To Subscribe:  ukha_xpl-subscribe@xxxxxxx
To Unsubscribe:  ukha_xpl-unsubscribe@xxxxxxx

xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.