Project
Subject: Re: HttpMethodBase.releaseConnection() finished download
Sven Köhler wrote:
>> 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 wil
Sven,
I've not tried this, but if you send a "Connection: close" header on the
request, the server should echo that on the response. If that header is
on the response from the server, the the "releaseConnection()" function
will (or at least it should) immediately close the connection, rather
t
Sven Köhler wrote:
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.
So what would you suggest how an abort should look
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.
So what would you suggest how an abort should look like? For me, a
bool
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.
So what would you suggest how an abort should look like? For me, a
bool
Hi Sven,
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.
- exten
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
