I'll be honest, I think going for a spec this early in the game is premature. Let's push the envelope on what we can do on top of this infrastructure, then standardise once we have a clue about what we are attempting to do. At this point we're still figuring out what we can do with this baby.
On Thu, Dec 31, 2009 at 1:03 PM, Mike Brown <[email protected]> wrote: > That clause basically says the license is conditional that you're not > making a stream ripper (the wording is vague enough however to be expanded > to any form of data storage) but looking closer at the spec it's more > multimedia centric than I first thought. Even without the licensing concerns > it's not the right one to pursue for the spec > > > On Wed, Dec 30, 2009 at 3:16 AM, Anthony Baxter > <[email protected]>wrote: > >> I don't think it would be possible to use RTMP for Wave, anyway, >> because the license would prohibit it: >> http://www.adobe.com/devnet/rtmp/pdf/rtmp_specification_license_1.0.pdf >> says it's only to be used for streaming audio/video. Quite the >> footbullet from Adobe, imho. >> >> (first noted, as far as I am aware, here: >> >> http://elliotmurphy.com/2009/12/23/rtmp-license-forbids-anyone-from-storing-data/ >> ) >> >> >> On Wed, Dec 30, 2009 at 10:01, Mike Brown <[email protected]> wrote: >> > Just curious if anyone has looked at adobe's RTMP (recently opened spec) >> at >> > first glance it looks like it would fit well for what a wave C/S >> protocol >> > would need. >> > >> > On Sun, Dec 6, 2009 at 6:24 AM, Jo hyphen el <[email protected]> >> wrote: >> >> >> >> If any dev people don't have preview accounts I have a few nominations >> >> going spare. send me an email. >> >> >> >> >> >> On Dec 6, 1:15 am, Michael K <[email protected]> wrote: >> >> > Guys, this discussion has moved to wave preview a long time ago. >> Those >> >> > of you who have accounts, can find the relevant waves by searching >> >> > "group:[email protected]<group%[email protected]> >> ". >> >> > >> >> >> >> -- >> >> >> >> You received this message because you are subscribed to the Google >> Groups >> >> "Wave Protocol" group. >> >> To post to this group, send email to [email protected]. >> >> To unsubscribe from this group, send email to >> >> [email protected]<wave-protocol%[email protected]> >> . >> >> For more options, visit this group at >> >> http://groups.google.com/group/wave-protocol?hl=en. >> >> >> >> >> > >> > -- >> > >> > You received this message because you are subscribed to the Google >> Groups >> > "Wave Protocol" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]<wave-protocol%[email protected]> >> . >> > For more options, visit this group at >> > http://groups.google.com/group/wave-protocol?hl=en. >> > >> >> >> >> -- >> Anthony Baxter, [email protected] >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "Wave Protocol" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<wave-protocol%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/wave-protocol?hl=en. >> >> >> > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > -- Brett Morgan http://domesticmouse.livejournal.com/ -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
