Quote:
Originally Posted by mdevour
We at least need to:
|
I think one thing to do is add support for "handshaking", to forums that connects to peer-servers on the same connection. That thing can be hard to explain, specially in english, but I'll try.
Client connects to port 119 as usual, but so are servers (peers that transfer the news). The difference between a peer and a client is the handshake string (not the authinfo). When a server-to-server connection is established, the string "MODE STREAM" are sent to identify the connection as non-human. Clients are sending "MODE READER" to identify as human readers. This hack does not do that, and that gives me some problems since I'm peering locally from the same server as the forum. I also use a suck-feed for some local groups which automatically makes me identified as a peer. So for now I have to use a dummy ip to connect as a client to the server. I tried to fix that part, but failed.
If a server is configured as a clientserver the "MODE READER" isn't necessary for the handshake, so it says "Hi, I'm a clientserver" first - and that's why this hack works so good.
If you're a peer, you have to send MODE READER if you don't want to peer. If a server is configured as a peering server (both methods are made by ip detection), the server immediately acts as streamingserver instead and you have to enter MODE READER to identify as a client. This is where the problems start. When I'm trying to download posts to the forum as a client, the server identify me as a peer and the posts never arrive.
To be short - handshake identification is needed in this hack.
And I'm also willing to help.