Re: Reserved bytes in peer-wire handshake

>From: extadi2000 <[email protected]>
> In order to establish that capabilities of the concerned clients, I
> have used the reserved bytes in the peer-wire handshake in a way which
> I feel conventional and convenient.  I set the value of the first byte
> to 0xFA to inform the remote side that I am conforming according to
> the format.  I leave byte-2 and byte-3 as 0x00 for future extensions
> which aren't client specific.  I set byte-4 and byte-5 as a unique
> client identifier (UCI), and leave byte-6, byte-7 and byte-8 for
> client specific data.  I think it would be good to define a standard
> here, and would like to know your comments regarding this and/or any
> incompatabilies this implimentation would have.

Okay, so...? What are you doing with them? It might be a good idea, or it
could be bad. No one can evaluate it, if you don't say anything about
what you're doing.

> I will be gone for two weeks so I will be unable to continue on this
> thread.

And as you should know, this is the worst possible time to propose
something new and not provide details.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \   (    |         [email protected] PGP 8881EF59         |    )   /
  \_  \   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
    \___\_|_/82 04 A1 3C C7 B1 37 2A*E3 6E 84 DA 97 4C 40 E6\_|_/___/




------------------------ Yahoo! Groups Sponsor --------------------~--> 
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/dkFolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/BitTorrent/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/