Re: Re: Web interface prototype

Hi Eivind,

This is a really good point.

We need a simple way to install and run the web interface for our=20=20
customers, putting the core server and the web server in one executable =
=20
is the easiest way to do this.  (Remember, this has to run on=20=20
Windows....)

If you want to take a different approach, you can look at the current=20=20
SLIMP3 server as the slimp3-core server.  Use the CLI or the HTTP API=20=20
and your favorite web development tools to build your application.  Let =
=20
us know what extensions you need to the slimp3-core server (I'd love to =
=20
extend the HTTP api to be able to respond with XML data for building=20=20
these kinds of meta applications, but so far nobody has needed it.)

-dean


On Thursday, February 20, 2003, at 03:23  AM, [email protected] wrote:

> On Wed, 19 Feb 2003, dean blackketter wrote:
>
>> I'd like to make sure that whatever back-end changes are made, we try
>> to make them as skin-neutral as possible.  This way when somebody new
>> comes up with a great new skin, they can build on the existing work.
>
> I've been wondering about that.
>
> Is there some logical reason why the web-interface and the=20=20
> slimp3-server
> are so tigth integrated as they are ?
>
> As I see it it is perfectly reasonable to run a slimp3-server with no
> web-interface at all, using only the interface on the slimp3 itself. It
> is also perfectly reasonable to have any other interface instead of, or
> in addition to the web one.
>
> In other words, I don't see what' so special about exactly
> control-by-web that it needs to be integrated into the slimp3-server
> itself.
>
> My preference would be to have a divison something like the following:
>
> * slimp3-core server. Does all communication with the slimp3-device.=20=20
> Has
>   a well-defined and _stable_ API that enables access from any other
>   program that migth desire so. API should essentially have all the=20=20
> same
>   functions the slimp3 itself has:
>   - Send commands to slimpe (play, pause, volume, display text, etc..)
>   - Ask for status (list of slimp3-devices, status of devices, current
>     volume etc..)
>   - query the Library in various ways
>   - manipulate the playlist in various ways.
>
> With this in place (And I think it mostly is really....) there is no
> reason any number of interfaces could not coexist, each one being
> completely independent, and completely optional. The slimp3 core server
> would not need to know anything about skins, html, http,
> http.basic authentication, https, or any of the other details of this
> particular interface.
>
> Sincerely,
> 	Eivind Kj=F8rstad
>
> ------------------------ Yahoo! Groups Sponsor=20=20
> ---------------------~-->
> Get 128 Bit SSL Encryption!
> http://us.click.yahoo.com/FpY02D/vN2EAA/xGHJAA/rIp0lB/TM
> ---------------------------------------------------------------------=20
> ~->
>
> To unsubscribe from this group, send an email to:
> [email protected]
>
>
>
> Your use of Yahoo! Groups is subject to=20=20
> http://docs.yahoo.com/info/terms/
>
>


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/FpY02D/vN2EAA/xGHJAA/rIp0lB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
[email protected]

=20

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/=20