would be a nice feature.
I was literally just typing this:
Am I just a crazy man, or does it make sense to build the PlexConnect capabilities into Plex Media Server (similar to the DLNA server).
As I see it, there are two main functions of PlexConnect: Act as a simple DNS caching proxy that spoofs "trailers.apple.com" (and could be configurable), and serve the correct XML and assets to the ATV to make everything work.
To me, the XML/assert server is just like the DLNA support in PMS, just a different format (I see a simple, extensible template system built into PMS to handle any similar interactions). So it seems (to me, at least) to make sense for this to be built into PMS.
The DNS proxy/cache is a tiny little bit of code. That can easily be added to PMS as well, and controlled with the same flag that enables the PlexConnect feature. Though, if there is an extensible template system, I see the PlexConnect and DNSproxy as two different features. And PlexConnect would be installed as a plugin (as would support for other system integrations that can be served with HTTP, like "Uncle Bob's Better PS3 Integration").
I really believe that if enough people request/vote for this, it might be added ;) Though, because of the way it works and 'hacks' its way around things, it might not become an official Plex part and stay community based.
The only concern is that Plexconnect functionality is dependent on apple not changing anything in how the ATV works. Does Plex want to be tied to something that might not be possible down the road.
The only concern is that Plexconnect functionality is dependent on apple not changing anything in how the ATV works. Does Plex want to be tied to something that might not be possible down the road.
What he said...
I think its better to hope for an app store on the Apple TV.
I do not believe this will ever be rolled into the official server.
It's a clever trick and quickly becoming a fully featured client but it's not an "official" means of getting plex on the ATV2/3.
I do not believe this will ever be rolled into the official server.
It's a clever trick and quickly becoming a fully featured client but it's not an "official" means of getting plex on the ATV2/3.
I'm all for an "official" client for ATV3, but until there is an ATV app store (which may or may not ever happen, and if it ever did, may or may not accept a Plex client), this is the most "official" way of getting Plex on an ATV. I've only used it a couple of days, but it is far better, easier and simpler than any other Plex client I've used (including PS3, Roku, Mac Mini and jailbroken ATV2): It just works.
I can understand reluctance to include a DNS proxy in PMS, but I don't understand the reluctance to include an extensible PlexConnect server to present the media library data in a flexible/template-able manner: In fact, a well-defined template structure would be a lot easier to update when/if Apple changes the trailers server.
I guess what I'm saying is:
1) I think PlexConnect provides the best user experience. It's use should be encouraged and marketed.
2) To make a system easier to use, simpler and more streamlined, PlexConnect should be built-in to PMS (with options to turn it on, of course).
3) I will help work through sticking points to make it clean and easy (Like root access for privileged port 80: authbind or iptables during PMS install.)
I asked that question like two month ago, somwhere at the beginning of the project: http://forums.plexapp.com/index.php/topic/65963-plex-webnodejs-and-xml-questions/?p=382665
Not sure if "Plex Inc." would have changed its opinion. Might be a good question to Elan...
Currently PlexConnect is "just" another Third-Party-Client, albeit with great support from the core Plex team (Elan, Trudge... I have seen others around as well).
While from an end user point of view it would be cool to have PlexConnect incorporated in PMS, from a developer point of view we would lose the ability to make daily, sometimes hourly, code changes and updates :( Maybe after the code stabilizes and updates need to be less frequent, but for the moment I'd rather have daily updates and bug fixes :)
Instead of putting it into the plex server, it might make more sense to actually put it out on the web and tie it into your myplex account. That would be the only way that makes sense in my mind. Having everyone run a local DNS server as part of PMS isn't really practical, but a web service offering from the plex team seems more possible.
I can see that especially if it is discovered how to provision dynamic apps on the appletv (like the WWDC app that just "appeared"). Then pointing it to a server out on the web that would provision the app would make huge sense but probably draw a whole lot of attention from Apple and almost certainly call for a swift patch.
We honestly need an appstore like yesterday.
The current need for the use of sudo on *nix is also an issue.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
