[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 asn):
Hm,
https://github.com/aeftimia/hexchat/commit/bff1134bc9d17e8e0532bcc99d3a77b975ba1946
is a bit weird. It seems like your non-blocking `connect()` never
succeeded (which makes sense, since you never connect to a remote host
instantly) and you turned it into a blocking `connect()`.
Problem with a blocking `connect()` is that hexchat will block till it
connects. Imagine this on the server-side, where the hexchat bot gets 100
''connect me!'' messages a second, and it blocks for every connect.
You will probably need to introduce some kind of asynchronous networking
there. You want to do a non-blocking `connect()` and run
`add_client_socket()` only when it's completed. Are you familiar with any
asynchronous Python networking libraries (like asyncore or twisted or
something)?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9022#comment:17>
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