Oleg,
after adding codec as another dependency and upgrading to 3.0-alpha2,
the jelly taglibs were all still working.
HTH,
On Tue, 28 Sep 2004 09:50:59 +1000, Dion Gillard <[EMAIL PROTECTED]> wrote:
> Oleg, I do care.
>
> I've just unfortunately been moving offices, had servers offline, had
>
Oleg Kalnichevski wrote:
<>...
St.Ack,
Could you retest HttpClient 3.0a3 with IBM JRE and let us know if the
problem still persists?
No problem. Soon as its available.
}
public int execute(HttpState state, HttpConnection conn)
throws HttpException, IOException {
return super.execute(
> That'd be grand if its possible (We like the IBM JVMs' speed and more
> detailed thread dumps). We used to subclass httpclient so we could do
> the below, moving the setting of the timeout till after the open.
> HttpClient 3.0 now sets timeout, etc., after the open seemingly so our
> subcla
Oleg Kalnichevski wrote:
We have already had a few reports regarding IBM JSSE semantical
incompatibilities with Sun JSSE. It appears IBM JSSE implementation
unlike Sun's does not like attempts to set socket parameters when the
socket is closed. I believe it is clearly a bug in IBM JSSE but we can
t
Hi St.Ack,
Your feedback is really appreciated. I am quite happy that we now have
one less development list to spam ;)
See my comments inline
> The upgrade took way longer than I anticipated, a couple of days rather
> than a couple of hours. While some of the time was spent on refactoring
> o
Hi St.Ack,
Many thanks for taking the time to make such a detailed response. I
haven't had time to fully digest (no pun intended) your message, but
I'll take a look at it again in the morning. In the mean time I've
added Heritrix to the applications page in CVS, which will be added to
the
Oleg Kalnichevski wrote:
Thanks, Adam
Should we decide to go on a spamming spree, these may also become
potential victims ;-)
Let me preempt the spam (smile).
I'm part of the webgroup at the Internet Archive (archive.org). We've
been using httpclient at the heart of our open source crawler Her
Eric,
The intention is to keep HttpClient 3.0 compile-compatible with
HttpClient 2.x (except for all that ugly stuff that has been deprecated
in 2.0). Feel free to submit a patch for the HttpException class.
Keep us posted on the progress
Cheers,
Oleg
On Wed, 2004-09-29 at 21:10, Eric Johnson w
Some feedback, finally.
I attempted to compile the "client" tools of the slide project with the
HttpClient 3.0 alpha release.
You'll probably not be surprised to hear that it didn't compile. It
turns out that a few missing functions in the HttpException class cause
the compile failures. I add
I have no problem with posting to the dev lists for these other
projects. My feeling is that we should keep it friendly and just
encourage people to have a look at 3.0 and then submit their
requests/ideas to httpclient-dev or bugzilla. Once we've done that I
think we'll just have to be happy
Thanks, Adam
Should we decide to go on a spamming spree, these may also become
potential victims ;-)
Oleg
On Tue, 2004-09-28 at 20:37, Adam R. B. Jack wrote:
> > > On Mon, 2004-09-20 at 22:50, Oleg Kalnichevski wrote:
> > > > As far as I know the following projects rely on HttpClient 2.0 as a
> > On Mon, 2004-09-20 at 22:50, Oleg Kalnichevski wrote:
> > > As far as I know the following projects rely on HttpClient 2.0 as a
> > > required or optional dependency
> > >
> > > * Apache Jakarta Slide (http://jakarta.apache.org/slide/)
> > > * Apache Jakarta Cactus (http://jakarta.apache.org/ca
Folks, shall we try to approach members of the projects listed below
(except Slide) directly? Apparently no one of them is monitoring this
list.
How does everyone feel about it?
Oleg
On Mon, 2004-09-27 at 20:43, Oleg Kalnichevski wrote:
> Sadly, no one seems to care. What do we do?
>
> Oleg
>
Oleg, I do care.
I've just unfortunately been moving offices, had servers offline, had
a firewall issue etc etc.
I should get to testing 3.0 with jelly rsn
On Mon, 27 Sep 2004 20:43:56 +0200, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote:
> Sadly, no one seems to care. What do we do?
>
> Oleg
>
Well, er, I care.
At least, I care about the Slide *client* library. I don't know if the
server stuff has a dependency on HttpClient.
I've been meaning to add it to my list to check how much it changes.
I'll do that this week. If I don't do it this week, it will be several
more weeks after t
Sadly, no one seems to care. What do we do?
Oleg
On Mon, 2004-09-20 at 22:50, Oleg Kalnichevski wrote:
> As far as I know the following projects rely on HttpClient 2.0 as a
> required or optional dependency
>
> * Apache Jakarta Slide (http://jakarta.apache.org/slide/)
> * Apache Jakarta Cactus
Jelly is going through a 1.0 release at the moment, but I think it's
worth looking at it before then.
On Tue, 21 Sep 2004 08:56:21 +0200, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote:
> I apologize for forgetting about Maven and Jelly. Are there any plans to
> evaluate HttpClient 3.0? We are tryin
I apologize for forgetting about Maven and Jelly. Are there any plans to
evaluate HttpClient 3.0? We are trying to get some feedback about the
new 3.0 API before the call the API freeze.
Oleg
On Tue, 2004-09-21 at 03:07, Dion Gillard wrote:
> Jelly and Maven both use httpclient.
>
>
> On Mon, 2
Jelly and Maven both use httpclient.
On Mon, 20 Sep 2004 22:50:20 +0200, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote:
> As far as I know the following projects rely on HttpClient 2.0 as a
> required or optional dependency
>
> * Apache Jakarta Slide (http://jakarta.apache.org/slide/)
> * Apache J
19 matches
Mail list logo
