Re: [In Development] RESTful API for LMS
expectingtofly <expectingtofly.a84fk0-NUepA2SMhDQqspMVqqL2D+4xXEVPTSb/[email protected]>
| Newsgroups | gmane.music.equipment.slimdevices.devel |
|---|---|
| Organization | Logitech Squeezebox Forums |
| Message-ID | <[email protected]> |
erland wrote:
> Great effort, Im looking forward to see this evolve. :-)
>
> It would be great to have a documented API thats less coupled with the
> user interface, but this will be a big work when you get to the browsing
> API parts unless you are going to re-implement all browsing code in LMS.
> Ive done that partly in Custom Browse plugin and we did that partly in
> ickStream plugin for local library but supporting it for music services
> (My Apps content) would be really hard. However, if you skip browsing
> part its more realistic.
>
>
That's interesting to hear your experience, I've put that to the back of
my list for the moment and see what it looks like when I get there!
erland wrote:
>
> If you want this to be included in the core LMS distribution I suspect
> there are going to be community developers that are a bit concerned
> regarding supporting another API implementation. We already have CLI and
> JSONRPC (which mostly relies on underlying CLI commands) but expecting
> community developers to support a REST API in core LMS distribution that
> re-implement logic rather than rely on underlying CLI/JSONRPC APIs is
> probably unlikely.
>
Yes, I suspect that to the be the case, as intimated in my original
post. And I have no expectations of anybody, my goal, as stated, is
just to get it to a level of maturity that it becomes useful/mature
enough to be considered for included in the LMS distribution. But who
knows, it may never get there. it's just a fun thing to do at thing to
do at the moment, I suspect I'll pick it up and put it down again over
time, and use it to get to know the inner workings of LMS.
erland wrote:
>
> The only issue with that is that full functionality clients/apps might
> not want to use an API that requires the user to install an extra
> plugin. You should probably target API support for more simple apps,
> like a player control app or a now playing display app.
>
Indeed. I can't argue with that. I'll plod my way through it and it
will get a larger scope through time.
erland wrote:
>
> I plan to make an RFID based remote control for my child in near future,
> if you have support for volume control and sending a playlist to a
> player by then I might try to use it.
Cool, it will certainly have those features early on. :-)
Stuart McLean
EXPECTINGTOFLY PLUGINS :
- *BBC Sounds* :
https://github.com/expectingtofly/LMS_BBC_Sounds_Plugin
- *Virgin Radio (UK)* :
https://github.com/expectingtofly/LMS_Virgin_Radio_Plugin
- *Times Radio* :
https://github.com/expectingtofly/LMS_TIMES_RADIO_PLUGIN
- *Global Player (UK)* :
https://github.com/expectingtofly/LMS_GlobalPlayer_Plugin
For BBC Sounds help see the 'BBC Sounds Wiki'
(https://github.com/expectingtofly/LMS_BBC_Sounds_Plugin/wiki).
------------------------------------------------------------------------
expectingtofly's Profile: http://forums.slimdevices.com/member.php?userid=63263
View this thread: http://forums.slimdevices.com/showthread.php?t=115143
_______________________________________________
developers mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/developers