[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #9022 [Pluggable transport]: Create an XMPP pluggable transport

#9022: Create an XMPP pluggable transport
---------------------------------+------------------------------------------
 Reporter:  asn                  |          Owner:  feynman 
     Type:  task                 |         Status:  accepted
 Priority:  normal               |      Milestone:          
Component:  Pluggable transport  |        Version:          
 Keywords:                       |         Parent:          
   Points:                       |   Actualpoints:          
---------------------------------+------------------------------------------

Comment(by feynman):

 Replying to [comment:39 asn]:
 > Also, where did the file transfer idea go? Does inbound file transfer
 (the one where files go through the server) work in Google's XMPP servers?

 I looked into the file transfer protocol and it seemed easier to make my
 own protocol than try to sneak all the parameters (port numbers, ip
 addresses, etc) into fields of an existing one. As far as I can tell, the
 chat server does not treat the file transfer protocol any differently than
 any other xml protocol, and it is really up to the users of the file
 transfer protocol to manage the actual exchange of data.

 I looked into what the file transfer protocol can do with regards to
 making sure data gets to the client and in the right order. It would seem
 I already have the same system of safeguards integrated into the hexchat
 protocol. I also have new things like dynamic throttling, dynamic rates at
 which sockets are read, and caching.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9022#comment:47>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs