On Aug 24, 2009, at 15:28, Mike Stay wrote:
> Here are some transport layers we'd be interested in having for
> running CapTP over:
Please CC CapTP discussion to the e-lang list <
e-lang@...-
os.org> to help keep everyone informed.
> 1. Polling over HTTPs for AppEngine
> 2. PostMessage for inter-frame comms
> 3. Flash's LocalConnection for inter-browser comms
> 4. Flash's sockets for arbitrary client-server comms in the browser
> 5. Web workers/gears
These all seem like reasonable ideas, but I'm not familiar with any of
the particular details of them.
My initial plan had been to first deliver a HTTP-based peer-to-peer
system, assuming each side is unNATed, unfirewalled, and both a HTTP
client and server, and then consider how to handle the in-a-browser
case.
Is there any particular one you would like me to research first, or,
if you are interested in working on them, information you would like
me to provide about what CapTP needs, or the implementation
architecture?
(To review, CapTP needs a transport which delivers messages, order-
preserving, with eventual notification of connection failure (periodic
pings is fine), in which both the initiator and the responder are
authenticated by public key, and messages cannot be read by any other
party.)
--
Kevin Reid <
http://switchb.org/kpreid/>
_______________________________________________
e-lang mailing list
e-lang@...
http://www.eros-os.org/mailman/listinfo/e-lang
