search

djspiewak / cccp

Common Colaborative Coding Protocol
119 stars 6 forks source link

add support for jabber transport #4

Open xeno-by opened 12 years ago

xeno-by commented 12 years ago

As far as I understand, currently all parties involved in CCCP must be connected to the same server instance. Not everyone has a static IP, so it'd be very helpful to be able to use Jabber as transport.

djspiewak commented 12 years ago

So, there are a whole raft of problems associated with supporting Jabber as a transport protocol. Fortunately, most of them are associated with federation, which isn't part of this request. :-) However, in general, working with Jabber is significantly more complex than working with raw HTTP, and in general, less firewall-compatible.

CCCP does not require that everyone have a static IP, only the server. In other words, its requirements are precisely the same as the requirements for a working Jabber server and client(s). Less restrictive, as a matter of fact, since CCCP is using HTTP as the transport protocol, which is generally more firewall-friendly than Jabber.

With that said, I'll leave this open. I won't implement this, but if someone wants to take it on as a project, I'll gladly merge the pull request! My only criterion is that the transport protocol be a pluggable option, rather than hard-coding Jabber over HTTP. HTTP should remain the default, as it is more compatible.