Asking with a hash, not for a hash, if we're going that way... I'm surprised to read replies like this here. The question is about possible protocols, devising which is a part of the problem, and you're asking me if I mean HTTP or FTP. Maybe try thinking this way: client has a hypothesis, sends a hash of it to the server. Server confirms. Then the client sends a hash of the hypothesis but reversed to avoid hash collision, and so on until certainty. Of course hashing is just, again, only symbolic here. It would have to be something more intelligent and tailor made for this problem in particular.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|