+1 vote: Having webbrowser based configuration instead of standalone swing UI should make UI layout and design tasks easier most of the people. Splitting a work dueties between a hardcore backend and UI layout issues, we have more html wizards than Swing ui wizards. And to be honest its where all apps go...the web2.0 and whatnot.

Jetty .jsp/servlet is an interesting one, its very small and embeddable still giving servlet/.jsp support. We could quite easily build a nice HTML ui screens and be accessible using PS3 browser at runtime. Very important issue if we run service in a basement home server. Another good one is Tomcat but its not as embeddable module.

I have videosites to PS3MS rss converter project. It's a .war webapp package. We had an internal Jetty/Tomcat engine could install 3rd party modules right into the PS3MS server.

This is where I would like us to forward PS3MS GUI, away from fat Swing/SWT UI to web application. I even could use my cellphone to admin dlna service.

Keep the PMS service/daemon configuration via beans, and create an admin listener on a well-known port. Then a separate admin server can be created, running inside or outside of a servlet container, and connect to the PMS service via the well-known port to send the admin commands. The protocol can be as simple or as complex as you like, but my preference would be SOAP WS.

Then your choice of servlet container becomes moot: release a war for those of us that use Tomcat on their server, and package a jetty distro if you want the rest of the known universe to be able to run it. In either case, the PMS service will still be a daemon/service that does the heavy lifting, while the (new) admin service can be a separate entity not heavily coupled to the main codebase.

It would also allow lightweight alternatives to this heavyweight servlet admin service, using a scripting language or whatever, as long as the admin port API was well defined.

Encapsulated, loosely-coupled, and customisable. Like all the best Java

Yes, a web UI for some of the common options that we all change now and again would be great. I also have the problem of running up and down stairs and also one of my servers is virtualized so I'd like to not have to RDP to it each time.

The most obvious candidate for web UI for me are:

o Managing the media content folder paths in PMS (add/remove/sort order)o AC-3 audio transcoding bit rateo An option to force a re-announce of the available contents.

If it is possible, it would be even better to have a RESTful API to the web UI backend so that if advanced users wanted to we could build our own interfaces. Nearly every component of my home theater system is IP enabled, including the plasma display, and soon the AV processor also. I'm looking to build a single of pane of glass type UI to the entire system.