Adobe To Open Real-Time Messaging Protocol
synodinos writes "Adobe has
announced plans
to publish the Real-Time Messaging Protocol specification, which is
designed for high-performance transmission of audio, video, and data between
Adobe Flash Platform technologies. This move that has followed the opening of
the AMF spec has been
received with varying degrees of enthusiasm from the RIA community."
..."Abobe"?!
I wonder if the RIAA will be as enthusiastic too..
Please? Can someone fix the topic?
Bad Timothy!
As I walk through the valley of death I fear no one, for I am the meanest sonova bitch in the valley!
This is good news for the haXe community.
when have they developed anything with peformance in mind ??? I wish I could stab PDFs in thier proprietry format face!
Flash is open. There is no open source viewer yet, but the specifications themselves have been there long enough.
As long as there are slaughterhouses, there will be battlefields.
Not really.
First, it's got the same problem as any other proprietary application which opens specs -- there's only one implementation, and that implementation is proprietary. Most specs at least include a reference implementation.
More importantly, how long have the specs been open? Last I checked, they were only open for developing anything but a client/viewer.
Don't thank God, thank a doctor!
Whew... By reading the topic alone, I thought someone "great! someone just reinvented IRC..."
I am convinced that I can always be convinced otherwise.
Hey, look, everyone, an Adobe employee shares his thoughts!
I'm not sure there's any point to this, since the Red5 guys have already documented and implemented the protocol. And Wowza has a fantastic implementation, even though it's not open source. If nothing else, I'd like to see "Abobe" explains the fucked-up connection handshaking. "Send me any ol' 1500 bytes! Ok great, you're connected!"
I think it's good that some companies, like Adobe, are realizing it makes good business sense to open up these protocols. However let's also be aware that Adobe is perfectly willing to tighten the screws further in other areas when they feel like THAT makes business sense. Anyone who (like me) uses any of their CS3 or CS4 products has dealt with this.
Actually, I should say the first install of CS3 or CS4 goes pretty well, and activation is painless. But if you've got it at home and at work - which is perfectly acceptable according to their EULA - then have a computer suddenly die, prepare to invest a lot of time in trying to get the licensing sorted out just so you can do your work.
So my (long-winded) point is: Good for Adobe, but let's not give them too much credit for this.
#DeleteChrome
May 2008 was when Adobe relicensed it to permit development of viewers.
The big parts not in that spec are Spark (the video codec, which I don't think Adobe CAN open up, I'm not sure it's all theirs) and RTMP. Now it's just Spark.
The AC original poster is a moron.
"You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time."
Hey, look, everyone, an Adobe employee has thoughts!
There, fixed that for you
Search on google for: gnash clean room
What you will find is that Adobe made it difficult to legally work on an open source viewer, and that the specs that exist are either (1) leaked, and therefore it is questionable whether you can legally use them, or (2) from a clean room reverse engineering.
From: http://lwn.net/Articles/270056/
Gnash development has been done using a Clean room reverse engineering technique. By agreeing to the license for the Adobe (formerly Shockwave) Flash player, a developer gives up the right to develop a competing product.
From: http://www.gnashdev.org/?q=node/30
Rob: The Adobe EULA for Flash forbids anyone who has installed their Flash tools or plugin from working on Flash technologies. This has had a chilling effect on the development of free Flash players, since a developer must either choose to decide that Adobe won't sue them over this, or to do what Gnash does, which is a slow and inefficient, clean room, reverse engineering project.
Adobe has declined to comment on this issue, since the confusion benefits their lockin of the market. Although Adobe has said they support Open Source projects, and donated Tamarin to Mozilla, we'd love to see a public statement that Gnash developers won't be subject to a lawsuit. It's very difficult to find developers that have never installed the Adobe software ever, which is what we've been doing to maintain our clean room approach.
From: http://www.openmedianow.org/?q=node/21
Savoye suggests that, "Most of this documentation, if we really wanted it, has already leaked out on the Internet years ago."
...embed a chat room in a PDF and talk to anyone who has a copy of the same PDF open.
Technoli
The bloat goes in before the name goes on.
"The ferrets, they're every where I tell you!"
Spark is just another name for H.263; you can get the spec from ITU. The undocumented proprietary codec is VP6, but ffmpeg has a reverse-engineered decoder.
How about "when have they developed something with security in mind"? Maybe I'm just bitter, but it seems like every week there's another handful of flash and acrobat exploits.
(Posting to remove moderation.)
Um, RTMP is not a chat protocol. It is a protocol for stateful connections with multiplexed streams for downloading large amounts of media with real-time responses and quality of service requirements. It is what the Flash Player uses to download audio and video from servers. See Wikipedia. Next time, look up the topic before spouting off.
Ah. Good news, then.
Even so, it's still got the same problem Silverlight does: The open source project has to catch up from the beginning (8 months of the spec being open vs 13 years of Flash), while the proprietary version marches ahead.
Not that it won't happen, but it will take time.
Don't thank God, thank a doctor!
And didn't they just steal and seal from RTSP?
http://en.wikipedia.org/wiki/Rtsp
If "Abobe" wants to do something good, they should allow their terrible payware FMS to serve up RTSP.
quis custodiet ipsos custodes
still, RTP+SIP or H.323 should do everything this does, unless it's got some uber-feature that at least one of those two doesn't have. which i doubt.
And Nellymoser, one of the audio codecs.
It's good that they're opening up RTMP but they just released RTMFP/Stratus which looks like it's going to be very interesting. I want to create a system based on top of RTMFP but I don't want that system to be at the mercy of Adobe. Hopefully someone (like the guys behind Red5) will reverse engineer the Stratus interface.
Me lost me cookie at the disco.
I hate megavideo with their IP recording. I hate the ones that use RTMP and don't let me download the flv file. So now I need the freeware developers to update their firefox addons and freeware apps Greasemonkey scripts to support Adobe's or Abobe's (hahah) open specs on the RTMP. I know orbit says it supports RTMP, but megavideo is impossible without getting your IP add changed.
http://manoj91.blogspot.com/
Second cousin do President Odama.
Odama must have a lot of balls.
Spark is just another name for H.263; you can get the spec from ITU.
And the patent license from whom? It has to be royalty-free in order to be compatible with free software.
That's why "open Flash" is a scam. Adobe gives you the specs but not the patent licenses (since they don't own many of the patents anyway) and tells you that you're all set to write your own open source Flash player.