On 04/08/11 17:37, Vincent Ladeuil wrote:
> What's wrong with transport.disconnect() ?
It requires the API user to care about the connection timeout.
E.g. something like:
<get some graph information from remote transport>
<potentially expensive processing of revisions>
<request some revisions from remote transport>
might or might not cause the connection to the remote host to time out,
depending on the timeout set on the local machine, the timeout set on
the remote machine and the amount of processing that has to be done.
On 04/08/11 17:37, Vincent Ladeuil wrote: disconnect( ) ?
> What's wrong with transport.
It requires the API user to care about the connection timeout.
E.g. something like:
<get some graph information from remote transport>
<potentially expensive processing of revisions>
<request some revisions from remote transport>
might or might not cause the connection to the remote host to time out,
depending on the timeout set on the local machine, the timeout set on
the remote machine and the amount of processing that has to be done.
Cheers,
jelmer