[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:22 xnyhps]:
> Replying to [comment:21 feynman]:
> > It seems that Gtalk will only deliver so many messages in a given
period of time. I tried other chat servers, and they are much slower. I
can NOT watch youtube videos with hexchat.
>
> Is there a reason you're passing all traffic through `<message>`
stanzas? Many servers will throttle those to avoid spam, `<iq>` stanzas
are a lot more likely to work well. You could look at
[http://xmpp.org/extensions/xep-0047.html XEP-0047: In-Band Bytestreams]
for how this can be done.
>
> In fact, you might be able to use that specification for the actual
content data (leaving the signaling to `<message>`s or other `<iq>`s),
that would hide the data making it look like ordinary file transfers.
This sounds like a good idea. I looked into `<iq>`s, but it seems they do
not come with enough text fields (although I could be mistaken). I need
four text fields to send a message:
- One for the client ip:port
- One for the server ip:port
- One for the actual data
- The JID of the computer that sent the message
Unless all four fields can be stuck somewhere in an iq message, this route
will not work. Maybe with some hacks I could be wrong, but at first
glance, this looks like a dead end.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9022#comment:23>
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