Re: [SWMP] Media Machines' initial design and code

chris wrote:
>  That is, at leasts two: high bandwidth, secure protocol over tcp/ip, 
> short payload, low latency protocol over udp.
As described in that paper I linked, the SWAMP design already can use 
TCPand/or UDP depending on the delivery requirements of a particular 
kind of message.  That is, some messages (like object instantiation) 
need guaranteed delivery, and are usually infrequent, suggesting TCP.  
Other messages (like position-changes) are streamed and need low 
latency, suggesting udp.  It's also valuable to use tcp as a fallback 
when udp ports are blocked by firewalls.

The initial implementation only roughs-in the UDP parts, though, that's 
not working yet.  But you'll see that some parts of the design (e.g., 
enveloping) are there to support UDP datagrams.
> And we may even be looking at different protocols for server-server, 
> client-server and client-client for ultimate scalable system.
Perhaps, but it certainly would be preferable if these architectural 
connections could use a unified protocol.
> On the practical front, I have managed to compile hydras for both 
> windows and linux and the local test works on my winxp client. Still 
> trying to get it to work accessing the remote linux server, but that 
> should be working soon - it might just be a matter of the port being 
> blocked.
Excellent.

jay


_______________________________________________
SWMP mailing list
SWMP@ietf.org
https://www1.ietf.org/mailman/listinfo/swmp