[
http://issues.apache.org/jira/browse/HTTPCLIENT-596?page=comments#action_12426864
]
Ortwin Glück commented on HTTPCLIENT-596:
-
Arnaud,
It's a known fact, that (Sun's) sockets don't react to Thread.interrupt(). The
only (?) way to
On Tue, 2006-08-08 at 21:13 -0600, Todd Wilson wrote:
Greetings,
Can't seem to find anything on this in Bugzilla or the list archives, so
I thought I'd throw it out to the group before submitting a bug.
...
If I try the HTTP request manually via telnet, here's what I get for the
HTTP
[
http://issues.apache.org/jira/browse/HTTPCLIENT-596?page=comments#action_12426875
]
Arnaud Masson commented on HTTPCLIENT-596:
--
Oleg,
1) I understand that the only way is to interrupt is to close the socket, but
it should be
[
http://issues.apache.org/jira/browse/HTTPCLIENT-596?page=comments#action_12426880
]
Ortwin Glück commented on HTTPCLIENT-596:
-
Arnaud,
Please elaborate how HttpClient could possibly notice a Thread.interrupt() call
and do an abort
[
http://issues.apache.org/jira/browse/HTTPCLIENT-596?page=comments#action_12426890
]
Arnaud Masson commented on HTTPCLIENT-596:
--
I agree, it is impossible to cancel directly Socket.read(),
That 's why I have suggested using a thread
[
http://issues.apache.org/jira/browse/HTTPCLIENT-596?page=comments#action_12426893
]
Oleg Kalnichevski commented on HTTPCLIENT-596:
--
class WorkerThread extends Thread {
volatile HttpMethod method;
public void
[
http://issues.apache.org/jira/browse/HTTPCLIENT-596?page=comments#action_12426904
]
Arnaud Masson commented on HTTPCLIENT-596:
--
Ortwin:
The code that requests aborting a composite operation don't have to know the
details.
In the
I can certainly understand not wanting to deal with this. From the
standpoint of an HttpClient user, the tricky part is that I can't think
of a workaround if I still want to be able to work with this site. The
only option I can think of would be to fork HttpClient and provide my
own fix, which I
Todd,
The question is not *how* to handle this in your code, but rather *if*!
That system is not speaking HTTP, but something else. Why bother at all?
If you can, you should speak to the operators of that system and make
them comply with the (at least the basic) HTTP standard.
Odi
Todd
Folks,
The message I am forwarding was sent to the HttpClient user list a while
ago. I think the changes proposed by Balazs are very reasonable.
Unfortunately Balazs never submitted the patch and did not return emails
I had sent him off-list. Nonetheless, I think we should consider
changing
Yep, seems to make sense.
Odi
Oleg Kalnichevski wrote:
Folks,
The message I am forwarding was sent to the HttpClient user list a while
ago. I think the changes proposed by Balazs are very reasonable.
Unfortunately Balazs never submitted the patch and did not return emails
I had sent him
Hey !
I am not sure if this is the right forum for this question, please redirect
me if this is not.
With that, here is a question ... from a novice really.
We have a situation where we need to send an XML file from our server to
another server..URL really (http:// abc.com/xyz.crspx). This URL
Veni,
This is the developer mailing list, but your question is a typical user
question. You may get more detailed information on the user list:
http://jakarta.apache.org/commons/httpclient/mail-lists.html
Yes, HttpClient seems like the way to go. Have a look at this sample
code which is part of
13 matches
Mail list logo
