Hi Vic, On Fri, Nov 19, 2010 at 4:21 PM, Vicary Archangel <[email protected]> wrote: > ...The output of AMF requests is actually bitwise formatted variables, seems > somewhat like a pattern of data type, some delimiters and the variable > contents....
Ok, not a problem in Sling. > > ...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.... Ok, not sure what you mean with "returns after function call", but it's easy in Sling to integrate a servlet that returns anything in response to a specific HTTP request - you can have complete control of what's written to the servlet output. > > 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).... Ok, so if you need TCP connections outside of the java servlet model you'll need to implement some server-side components that manage sockets as needed and implement the protocol. Sling doesn't put any limitations on this, you can create an OSGi service that implements any suitable protocol. Hope this helps! -Bertrand
