Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Technology

Are There Alternatives to UPnP? 56

semanticgap asks: "I am thinking of putting together a PC based home entertainment system (media server in the basement talking to various computers around the house and controllable via some sort of a remote control device, etc.) as a fun project with emphasis on writing software. I've been reading up on the current state of affairs, and it looks like the protocol for this sort of a thing is UPnP (Universal Plug-n-Pray). It seems to provide all the functionality I want, but I don't like the fact that it is developed by Microsoft, nor do I like it in general - it relies heavily on things like UUID's, HTTPMU and other Microsoft-ish hacks. So I thought I'd ask Slashdot community - is UPnP going to gain acceptance, or are there alternatives to it?"
This discussion has been archived. No new comments can be posted.

Are There Alternatives to UPnP?

Comments Filter:

  • It can hardly be universal if it is proprietary to Microsoft. Instead, it will be Microsoft-centric and doubtful that other operating systems would use it.
  • by Anonymous Coward
    Sure, just watch the WB-P instead. No one is forcing you to watch T'Pol on Enterprise, you know!
  • Rendezvous, Jini (Score:3, Informative)

    by Anonymous Coward on Thursday September 26, 2002 @01:11PM (#4337554)
    • Yes, but Rendezvous is merely a protocol for automatic network configuration and discovering services (and a really good one too). UPnP goes a step further by providing means for device interaction.

      The point is that if I were to write a piece of UPnP capable software, when the UPnP DVD players (or whatever) come out, chances are this software will be able to work with it. With Rendezvous - the device-specific interface is undefined.

      Jini seems to be a Java-specific thing, so I'm not really interested in it.
  • The fact the uPnP is being thrust upon the world by Microsoft guarantees that it will be a winning "standard" (gag). Already it is widely deployed on Win2k and XP and as these system's market penetration continues, after a while everyone will have it.

    You, however, asked if there are alternatives. Of course there are. None will likely have the market penetration that uPnP will have but a possibly strong contender will be Apple's Rendevzous [apple.com], recently announced here on Slashdot. [slashdot.org] It uses Apple's "Open Source" license.
  • by Anonymous Coward on Thursday September 26, 2002 @01:56PM (#4337928)
    is UPnP going to gain acceptance, or are there alternatives to it?

    There are no alternatives, you dumbass. It's universal plug and play.

  • by maggard ( 5579 ) <michael@michaelmaggard.com> on Thursday September 26, 2002 @02:11PM (#4338050) Homepage Journal
    Apple just Open Sourced their Rendevous code, see the recent /. story on that here [slashdot.org]. Rendevous is an implementation of Zeroconf which is which is, in a larger sense, what you're looking for.

    Also note that MS isn't the only folks supplying UPnP, Intel also developed a lot which is now Open Sourced.

    Rendevous & Zeroconf information:

    Here's an earlier Apple implementation called SLP (RFC 2608) also used by Novell:

    Finally, for completeness here is UPnP:

  • Jini [sun.com] is a java based service delivery system that is a great alternative to UPnP. I'm currently working on a network based music player so I can play mp3's on my home stereo and control it from anywhere with a web browser.
    • Jini's probably the #1 competitor to UPnP, but unfortunately, it's Java only, so it's hardly competition. If you don't do Java, you don't do Jini. This precludes it from the really low end (read: cheap) devices like lamps.

      UPnP can be made really, really small and go on super cheap devices. Jini's architecture is cool, but it's got the darned Java albatross to carry around with it. Were it not for that, it may have had a chance.

      We considered making Jini products, but gosh, it just didn't seem to scale down well enough.

      By the way, don't use Intel's protocol stack as an example of how small UPnP can be. Size wasn't their primary concern, and it's as much as 10x as big as other stacks.
  • a few notes on UPnP (Score:5, Informative)

    by lembree ( 53531 ) on Thursday September 26, 2002 @03:00PM (#4338545)
    My company (Metro Link, Inc., www.metrolink.com [metrolink.com]) is a member of the UPnP forum, develops UPnP technology for Linux and other OSs that typically end in 'x', and was recently elected to the UPnP steering committee. You may remember us for our commercial X servers, Motif, OpenGL, etc. Most people who know us will tell you that we're pretty openminded, and contribute a lot to the open source universe (remember us when you X server magically loads up its modules instead of having to be compiled in). I'll try to lend some insight to help balance out religious arguments.

    First, let me address UPnP and Microsoft. Yes, UPnP was originally conceived by MS, and MS has written themselves onto the steering committee forever. However, the UPnP membership agreement precludes any member from owning the technology outright, and says that anyone who offers technology to the forum must do so without encumberance. Even Microsoft. UPnP is NOT proprietary to MS.

    Second, the technology. Everything in UPnP can be had for free. We've developed (and are successfully selling) two UPnP protocol stacks, one in ANSI C and one in Java. This was all home-grown, and we didn't need to license anything from anyone except the UPnP forum.

    As mentioned before to use the technology, you need to be a UPnP Forum member. Membership is free, and the only real restriction is that anything you suggest for inclusion be done so without encumberance. Anyone can join. If you join, and don't want to donate technology, then don't bring it up. It's as easy as that.

    The underlying standards are either pre-existing standards or build by the UPnP Forum. A case in point is Auto-IP, which does the ad-hoc network configuration. It's based on an IETF draft (draft-ietf-ipv4-autoconfig-05), which was originally authored by someone at Apple. I wouldn't be too surprised if it's very similar to Auto-IP. It's too bad that Apple didn't get involved earlier, we'd only have one uniform way to do this, instead of two Again, this isn't a MS invention.

    There are a lot of UPnP implementations available. Intel did indeed provide a GPL protocol stack that you can download from their site. It builds on Linux nicely, and give you sample apps, etc. We have our two stacks that will begin appearing in cheap applicances Real Soon Now (tm) thanks to our silicon-builder-friends.

    Alternatives to UPnP? Not really, at least not in one place. Many folks who responded to this message address only the Auto-IP part, where the box gets its IP address (FYI, Auto-IP on a net with DHCP is pretty much just DHCP). What they're missing is the juice of UPnP, where there's a protocol for device discovery and control. All the control and discovery is without any a-priori knowlege or configuration! (N.b., UPnP and Plug&Play are entirely different beasts: UPnP is on a network, Plug&Play and Kudzu are a single box)

    E.g., your UPnP PVR is on a net with your UPnP phone (they're both coming). They know about each other, thanks to UPnP. Phone rings, PVR pauses automatically and puts up caller ID. You pick up the phone, talk, hang up, PVR starts again. Your washing machine tells you it's time to switch the load over, not only on the TV, but on your UPnP Zaurus or iPaq (reality today), or perhaps your electronic picture frame. You want to listen to your MP3 library from your home server. Easy. Your iPaq, Zaurus, stereo receiver, anything, knows in advance how to search for media sources, get a list of titles available, and start spooling it down. Click and go.

    Our demos are much, much cooler than that even, but I don't know how much I can say.

    To answer your question, sure there are alternatives, but they're in many disjoint parts. I'd suggest getting Intel's kit, and playing with it, seeing what you can do with it. Whether you do that, or play with disjoint parts, you'll be experimenting, but UPnP will take off fairly soon now.

    • A case in point is Auto-IP, which does the ad-hoc network configuration. It's based on an IETF draft (draft-ietf-ipv4-autoconfig-05)....too bad that Apple didn't get involved earlier, we'd only have one uniform way to do this, instead of two.

      I think you should read the referenced document [zeroconf.org] more carefully, and follow the links in the post above yours [slashdot.org] you'd find that the IP auto-configuration method used by Apple Rendezvous and Microsoft UPnP is identical. It's all based on what the zeroconf guys did.

      Yes both Apple's and Microsoft's solutions go further, but at the low level this stuff does interoperate.

  • "[Regarding UPNP]It seems to provide all the functionality I want, but I don't like the fact that it is developed by Microsoft"

    See, this is what defines a dumbass. The functionality is provided, the technology is here, you admit that this is what you need, but then you disparage it just because it was developed by microsoft. Swallow your perceived pride and just use the damn stuff instead of looking for a less-functional alternative.
  • The IEEE Computer Society [computer.org] Magazine published in August an article on this topic. There are a lot of alternatives to UPnP: Sun, Hewlett-Packard, Apple, etc.

    Unfortunately, I don't have the magazine here, so I cannot say much. Here [computer.org] is the index of the magazine, here [computer.org] abstract of the article, and here [computer.org] is the article in PDF (but you must pay 19$ US for it).

    If you are actually interested, e-mail me (pgq AT poboxes DOT com) and I'll send you a summary.

He has not acquired a fortune; the fortune has acquired him. -- Bion

Working...