Hi Bertrand, The output of AMF requests is actually bitwise formatted variables, seems somewhat like a pattern of data type, some delimiters and the variable contents.
Basically AMF RPCs does not require channels other than HTTP, even with data returns after a function call. Tho whole serialization/deserialization process only touches raw POST data and the http output stream, in byte level. I believe if PHP can handle this, Sling should be able to do it even better as long as it is based on Java. What I seek more than AMFPHP is RTMP streams, which allows the client to do true video streaming, in contrast to the PHP's pseudo streaming. RTMP streams, which must then implemented with TCP connections, also enables some Flash things called Remote Shared Object, this involved in communication between http request threads with some sort of synchronized data (either in memory or file system). There is two major open source AMF server that already implemented RTMP streaming, written in Java. Red5 Server: http://osflash.org/red5 BlazeDS: http://opensource.adobe.com/wiki/display/blazeds/BlazeDS You can read the spec of RTMP alone here at http://www.adobe.com/devnet/rtmp.html. Hope I make it clear enough. =] Vic On Fri, Nov 19, 2010 at 5:29 PM, Bertrand Delacretaz <[email protected] > wrote: > Hi Vic, > > On Fri, Nov 19, 2010 at 3:43 AM, Vicary Archangel <[email protected]> > wrote: > > ...The question is how does Sling handle streaming? And can it send > binary data > > directly with pure JavaScript but not template things?... > > As Felix said, yes, using the HTTP request/response model. > > > In fact I'm seeking the possibility to implement an AMF-HTTP channel in > the > > future. > > Where can we find a quick description of AMF-HTTP? > > I looked at http://en.wikipedia.org/wiki/Action_Message_Format and > that seems to imply that the client switches to something else than > HTTP after the initial request to the gateway URL. That would be > possible with Sling, but not out of the box. > > -Bertrand >
