The only sure way to close the connection, at least for the moment, is to get hold of the HttpConnection and call close() on it. The following options come to mind:
- implement/override your own connection manager so that you have direct access to the connections created.
- extend the Method in question and override the execute() method. This will give the access to the connection that is being used to execute the method.
Adding the ability to abort methods is planned for the 2.1 release, but I don't think anyone has begun work on it yet. If you come up with a good solution that you are willing to submit we would be happy to make use of it.
Thanks,
Mike
On Nov 13, 2003, at 8:21 PM, Sven Köhler wrote:
Hi,
it seems that releaseConnection finishes the http-download until it is complete. I don't want that. I'm looking for a way to close the HttpConnection if the download wasn't completed yet.
I'm aware that one cannot "abort" a Http-Transfer without closing the connection and therfor loosing it for keep-alive etc.
There doens't seem to be a way of closing the HttpConnection by using the HttpMethodBase-Object. What should i try next?
Thx Sven
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
