[Free] getting started

. m a r c o s a u g u s t o chadart at gmail.com
Thu Sep 1 09:46:59 PDT 2005


getting back to vagina,
 
i placed David Rorex message as a walkthrought...
http://www.osflash.org/doku.php?id=rtmp_os

Looks like we got the handshaking so far...

What is useful to I include, like for example this:
0000  00 0c 76 bd a7 0a 00 0c  76 c9 ca 03 08 00 45 00   ..v..... v.....E.
0010  00 57 c8 8f 40 00 80 06  b0 89 c0 a8 00 36 c0 a8   .W.. at ... .....6..
0020  00 01 12 37 07 8f ee ac  10 79 b6 1c 28 99 50 18   ...7.... .y..(.P.
0030  80 6f da fc 00 00 43 00  00 57 00 00 27 13 00 08   .o....C. .W..'...
0040  70 6f 73 69 74 69 6f 6e  00 00 04 49 00 00 00 00   position ...I....
0050  00 00 00 00 03 00 00 00  0c 00 01 78 00 40 60 16   ........ ...x.@`.
0060  66 66 66 66 67                                     ffffg            


I think its this part:
3. Client → Server calls (aka rpc?)

There's more data I could include to help who know what to do with this ?
heheh


On 9/1/05, john grden <neoriley at gmail.com> wrote:
> Perfect thanks Ethan - 
>  
>  I'll go ahead and make up the PROTOCOL and SERVER sub pages then
> 
> On 9/1/05, Ethan Sutin <sutin at virginia.edu > wrote:
> > I have FCS installed and I'll update the wiki with the protocol comm I
> > observe.
> > john grden wrote:
> > 
> > > Yes, that makes total sense to me on all 3.  AFAIK, it's reasonable to
> > > assume they're sending chunks.  I guess my question is: does that
> > > enable you to add keyframes to a video stream that you've defined 
> > > elsewhere?  I don't know anything about streaming, so what do you
> > > think about that question?
> > >
> > > Yes, agreed, let's get the ball rolling on Protocol and Server
> > > threads.  to suppport those threads, we should have a common reference 
> > > page on the wiki - yes?  Shall I go ahead and see if we can edit
> > > Charle's stuff? or should I just start a fresh one and reference his?
> > >
> > > let me know, and we'll get it going,
> > >
> > > On 9/1/05, *Luke Hubbard ( luke at codegent.com
> > > <mailto:luke at codegent.com>)* < king.selassie at gmail.com
> > > <mailto: king.selassie at gmail.com>> wrote:
> > >
> > >     Hi John,
> > >
> > >     Im not a codec junkie, but I do enjoy playing with amf and java
> > >     servers. I agree we should lay the foundations (sessions, shared 
> > >     objects, streaming mp3) then others will join to add support for
> > >     other codecs. I guess it all depends on whether flashcom does some
> > >     form of encryption of the stream of video. Thinking about it this 
> > >     is quite unlikely. So really we have 3 parts.
> > >
> > >     1. communication protocol: amf layer for session control, shared
> > >     objects, etc
> > >     2. streaming server: streaming chunks of data, mp3, video. my 
> > >     guess is that it doesn't care what the codec is.
> > >     3. a/v processing: encoders, decoders, codecs (e.g. reading an avi
> > >     and converting to on2 or spark on the fly)
> > >
> > >     We should focus on the first two like you suggested. 
> > >
> > >     I'm not sure we could do 3 without understanding the codecs or
> > >     getting into a legal mess. So we should probably design this to be
> > >     extensible by 3rd party developers both open source and 
> > >     commercial. If we build a solid foundation, why wouldn't the
> > >     owners of the codecs want to sell plugins for the server. I can
> > >     also see people plugging this part into existing systems.. Perhaps 
> > >     a jni interface to ffmpeg on linux.
> > >
> > >     So where should we start..
> > >
> > >     [PROTOCOL]
> > >     Lets keep collecting raw streams which we can analyze to work out
> > >     the communication protocol. This should be documented on the wiki. 
> > >     David has started on this.
> > >
> > >     [SERVER]
> > >     Build a server which runs as a servlet for RTMPT and opens a tcp
> > >     port for RTMP. This needs to be extreamly scaleable so its
> > >     probably a good idea to use non-blocking sockets, mapped buffers, 
> > >     etc.
> > >
> > >     Should we start a thread for each of these tracks?
> > >
> > >     -- luke
> > >
> > >     Links:
> > >     http://ffmpeg.sourceforge.net/index.php 
> > >     http://www.springframework.org/
> > >
> > >
> > >
> > >
> > >     On 9/1/05, *john grden* <neoriley at gmail.com 
> > >     <mailto:neoriley at gmail.com> > wrote:
> > >
> > >         Hey guys, sorry about the late reply on this, I've been
> > >         struggling to get the filter setup in gmail, and I didn't even 
> > >         see the posts till now ;(
> > >
> > >         David, that list is an excellent overall view - agreed.
> > >
> > >         I know I said it on the other list, but I'd suggest we all
> > >         talk about and agree on one thing to focus on in that list and 
> > >         then get a prototype working.
> > >
> > >         FCS has 2 ares - streaming and shared object/push
> > >         technologies.  Both are obviously extremely important to the
> > >         effort. 
> > >
> > >         So, my first question is:  is there a codec junky in the bunch
> > >         we have here?  Chris Allen was right, we need a codec person
> > >         for the streaming media portion of all this - wouldn't you 
> > >         agree?  are we off in this thought?
> > >
> > >         Do you guys agree with this?  My thought was, if we get one
> > >         aspect of hit flying and working well (say shared
> > >         objects/server side classes/objects), we'd probably see a big 
> > >         influx of people who'd want to jump on board to get involved
> > >         with the OS project and then we might have a great lot to
> > >         choose from in getting a decent code person.
> > >
> > >         Thoughts? suggestions?  what do you guys think?
> > >
> > >
> > >
> > >         On 9/1/05, *David Rorex* <drorex at gmail.com
> > >         <mailto: drorex at gmail.com>> wrote:
> > >
> > >             Ok there are a few different things that need to be
> > >             captured / re implemented.
> > >
> > >             I think this is an exaustive list: (feel free to expand on
> > >             / add more
> > >             if i missed any, or correct me if i'm wrong anywhere)
> > >
> > >
> > >             1. Client <-> Server connection / handshaking
> > >             2. Client -> Server requesting / setting up a shared object
> > >             3. Client -> Server calls (aka rpc?)
> > >             4. Client -> Server making a change to a shared object
> > >             5. Server -> Client calls (aka rpc?)
> > >             6. Server -> Client notifying of shared object changed
> > >             7. Client -> shared object calls - this one's more
> > >             tricky...basically
> > >             sends an event to everyone (both server and client i
> > >             believe) that is
> > >             'connected' to the same shared object
> > >             8. Server -> shared object calls - see above
> > >             9. Server -> Client mp3 streaming 
> > >             10. Server -> Client flv streaming
> > >             11. Client -> Server asking for mp3 / seeking / pausing
> > >             12. Client -> Server asking for flv / seeking / pausing
> > >
> > >             I'm assuming a lot of these will share the same structure.
> > >             As was said
> > >             before, it 99% most likely uses a protocol very similar or
> > >             even the
> > >             same as the AMF format for transfering data / objects
> > >
> > >             -David R
> > >
> > >            
> _______________________________________________
> > >             Free mailing list
> > >             Free at osflash.org <mailto:Free at osflash.org>
> > >            
> http://osflash.org/mailman/listinfo/free_osflash.org 
> > >            
> <http://osflash.org/mailman/listinfo/free_osflash.org>
> > >
> > >
> > >
> > >
> > >         --
> > >         John Grden - Blitz 
> > >         _______________________________________________
> > >         Free mailing list
> > >         Free at osflash.org <mailto:Free at osflash.org >
> > >        
> http://osflash.org/mailman/listinfo/free_osflash.org
> > >
> > >
> > >
> > >
> > >
> > >     --
> > >    
> -----------------------------------------------------------------
> > >
> > >     Prepare to be locked out of the circle of trust.
> > >     http://www.againsttcpa.com/tcpa-faq-en.html
> > >
> > >     _______________________________________________ 
> > >     Free mailing list
> > >     Free at osflash.org <mailto:Free at osflash.org>
> > >    
> http://osflash.org/mailman/listinfo/free_osflash.org
> > >
> > >
> > >
> > >
> > >
> > > --
> > > John Grden - Blitz
> > >
> >
> >------------------------------------------------------------------------
> > >
> > >_______________________________________________
> > >Free mailing list
> > >Free at osflash.org
> > > http://osflash.org/mailman/listinfo/free_osflash.org
> > >
> > >
> > 
> > 
> > _______________________________________________
> > Free mailing list
> > Free at osflash.org
> > http://osflash.org/mailman/listinfo/free_osflash.org
> > 
> 
> 
> 
> -- 
> John Grden - Blitz 
> _______________________________________________
> Free mailing list
> Free at osflash.org
> http://osflash.org/mailman/listinfo/free_osflash.org
> 
> 
> 


-- 
. m a r c o s    a u g u s t o  ;



More information about the Free mailing list