user2029: When sending a getwork request, one always includes an id value. Does this value have any meaning? Will it cause problems to have multiple miners use the same id? Furthermore, if I wanted to send some extra information to a mining pool server, would id be an okay place to do it or should I add my own extra field?

user323: If you are talking about the Bitcoin API, getwork only requires data field, which is a place to put your solution.
However, I do believe that you are talking about the id field of a JSON RPC command. It is used to identify a response to a given request. Generally, it might not be the best place to put extra information. There are already a few extensions to the getwork protocol that you might want to use instead.

2029: <p>When sending a <code>getwork</code> request, one always includes an <code>id</code> value. Does this value have any meaning? Will it cause problems to have multiple miners use the same <code>id</code>? Furthermore, if I wanted to send some extra information to a mining pool server, would <code>id</code> be an okay place to do it or should I add my own extra field?</p>
 323: <p>If you are talking about the <a href="https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list" rel="nofollow">Bitcoin API</a>, getwork only requires <code>data</code> field, which is a place to put your solution.</p>

<p>However, I do believe that you are talking about the <code>id</code> field of a <a href="http://json-rpc.org/wiki/specification" rel="nofollow">JSON RPC command</a>. It is used to identify a response to a given request. Generally, it might not be the best place to put extra information. There are already a few <a href="https://en.bitcoin.it/wiki/Getwork" rel="nofollow">extensions to the getwork protocol</a> that you might want to use instead.</p>
