In NioProcessor .java you got the following select implementation :
@Override
protected boolean select(int timeout) throws Exception {
return selector.select(1000) 0;
}
The hard-coded 1 sec value smell fishy, it's normal ? if so I think
I'll place a comment for indicate it's not a mistake.
On Mon, 04 Feb 2008 22:02:19 -0700
Jeff Genender [EMAIL PROTECTED] wrote:
Mike Heath wrote:
To clarify, my understanding of pipelining is that it is sending
multiple requests and then waiting for the corresponding responses.
This is more than HTTP keep alive which would also allow
On Mon, 04 Feb 2008 18:52:37 -0700
Jeff Genender [EMAIL PROTECTED] wrote:
great question..Im interested in this as well.
Jeff
Sangjin Lee wrote:
I had a quick question on the connect timeout...
The connect timeout supplied to connectors is in the unit of
seconds, and it appears the
On Feb 5, 2008 9:17 AM, Julien Vermillard [EMAIL PROTECTED] wrote:
On Mon, 04 Feb 2008 18:52:37 -0700
Jeff Genender [EMAIL PROTECTED] wrote:
great question..Im interested in this as well.
Jeff
Sangjin Lee wrote:
I had a quick question on the connect timeout...
The connect
+1 - not enough granularity with seconds.
Alex
On Feb 5, 2008 3:53 AM, Maarten Bosteels [EMAIL PROTECTED] wrote:
On Feb 5, 2008 9:17 AM, Julien Vermillard [EMAIL PROTECTED] wrote:
On Mon, 04 Feb 2008 18:52:37 -0700
Jeff Genender [EMAIL PROTECTED] wrote:
great question..Im interested
On Tue, 5 Feb 2008 09:53:27 +0100
Maarten Bosteels [EMAIL PROTECTED] wrote:
On Feb 5, 2008 9:17 AM, Julien Vermillard [EMAIL PROTECTED]
wrote:
On Mon, 04 Feb 2008 18:52:37 -0700
Jeff Genender [EMAIL PROTECTED] wrote:
great question..Im interested in this as well.
Jeff
Thanks Julien this is cool.
Trustin why isn't any of this code documented? Would be nice if users can
see what this is about ... might make people use it more.
Alex
On Feb 5, 2008 3:07 AM, Julien Vermillard [EMAIL PROTECTED] wrote:
On Mon, 04 Feb 2008 22:02:19 -0700
Jeff Genender [EMAIL
On Feb 5, 2008 10:04 AM, Julien Vermillard [EMAIL PROTECTED] wrote:
On Tue, 5 Feb 2008 09:53:27 +0100
Maarten Bosteels [EMAIL PROTECTED] wrote:
On Feb 5, 2008 9:17 AM, Julien Vermillard [EMAIL PROTECTED]
wrote:
On Mon, 04 Feb 2008 18:52:37 -0700
Jeff Genender [EMAIL PROTECTED]
connector.setConnectTimeoutInMillis(250);
This satisfies both of you :)
My 2 cents ^^
Cordialement, Regards,
-Edouard De Oliveira-
http://tedorg.free.fr/en/main.php
- Message d'origine
De : Maarten Bosteels [EMAIL PROTECTED]
À : dev@mina.apache.org
Envoyé le : Mardi, 5 Février 2008,
On Feb 5, 2008 11:07 AM, Emmanuel Lecharny [EMAIL PROTECTED] wrote:
Maarten Bosteels wrote:
I agree that nobody will pass in hours or days, but IMHO it improves
readability a lot:
connector.setConnectTimeout(250, TimeUnit.MILLISECONDS);
or
connector.setConnectTimeout(250);
Maarten Bosteels wrote:
On Feb 5, 2008 11:07 AM, Emmanuel Lecharny [EMAIL PROTECTED] wrote:
Maarten Bosteels wrote:
I agree that nobody will pass in hours or days, but IMHO it improves
readability a lot:
connector.setConnectTimeout(250, TimeUnit.MILLISECONDS);
or
This sounds like an excellent approach to merging the efforts.
Rick
Mike Heath wrote:
I've been looking into merging
http://svn.apache.org/repos/asf/geronimo/sandbox/async-http-client-mina2/
into http://svn.apache.org/repos/asf/mina/asyncweb/trunk/client/ and I'm
trying to figure out the best
Wow...this is awesome...I could have used this because this is
essentially the same mechanism I wrote in AHC ;-)
Yeah...this should be documented in the FAQ somewhere as this would come
in handy.
Jeff
Julien Vermillard wrote:
Hi,
Just by the way, if you want to monitor a request/response
On Tue, 05 Feb 2008 13:55:15 +0100
Niklas Therning [EMAIL PROTECTED] wrote:
You would also need to make sure that the current IoConnector
implementations can support millisecond timeouts. I think that would
mean that AbstractPollingIoConnector.Worker needs to be changed.
Specifically the
On Feb 5, 2008 10:07 AM, Alex Karasulu [EMAIL PROTECTED] wrote:
Thanks Julien this is cool.
Trustin why isn't any of this code documented? Would be nice if users can
see what this is about ... might make people use it more.
see
Right, that's why I said the connect timeout limitation seems tied to the
select timeout...
Hard-coded 1 second select timeout will interfere with sub-second connect
timeout value. One obvious suggestion is to set the select timeout to be
the same as the connect timeout. That way, we're pretty
Excellent thanks.
Alex
On Feb 5, 2008 9:50 AM, Maarten Bosteels [EMAIL PROTECTED] wrote:
On Feb 5, 2008 10:07 AM, Alex Karasulu [EMAIL PROTECTED] wrote:
Thanks Julien this is cool.
Trustin why isn't any of this code documented? Would be nice if users
can
see what this is about ...
Hi,
I commited a few change to aweb :
- a ServiceResolver who use regexp for match service :
org.apache.asyncweb.server.resolver.PatternMatchResolver
- a HttpService for simply serving static files
org.apache.asyncweb.examples.file.FileHttpService
with it's FileMain for running a test server
Merge AHC into AsyncWeb client
--
Key: ASYNCWEB-2
URL: https://issues.apache.org/jira/browse/ASYNCWEB-2
Project: Asyncweb
Issue Type: Task
Reporter: Mike Heath
We need to merge the AHC code in
We don't have any any real benchmarks for AsyncWeb yet. At least, I'm
not aware of any extensive benchamrks. I would like to see this change
in the near future. After all, you can't improve performance if you're
not measuring it.
That being said, the Yaws benchmark you sent is contrived and I
[
https://issues.apache.org/jira/browse/DIRMINA-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated DIRMINA-527:
Attachment: DIRMINA-527.patch
A proposed patch (based on the trunk).
- Introduces
[
https://issues.apache.org/jira/browse/DIRMINA-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated DIRMINA-527:
Attachment: (was: DIRMINA-527.patch)
should be able to set connect timeout in milliseconds
[
https://issues.apache.org/jira/browse/DIRMINA-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangjin Lee updated DIRMINA-527:
Attachment: DIRMINA-527.patch
should be able to set connect timeout in milliseconds
should be able to set connect timeout in milliseconds
-
Key: DIRMINA-527
URL: https://issues.apache.org/jira/browse/DIRMINA-527
Project: MINA
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/ASYNCWEB-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Heath reassigned ASYNCWEB-2:
-
Assignee: Mike Heath
Merge AHC into AsyncWeb client
--
[
https://issues.apache.org/jira/browse/ASYNCWEB-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565892#action_12565892
]
Mike Heath commented on ASYNCWEB-2:
---
AHC has been merged into AsyncWeb Client as revision
[
https://issues.apache.org/jira/browse/DIRMINA-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565898#action_12565898
]
Sangjin Lee commented on DIRMINA-528:
-
Yeah I noticed that too...
NioSocketConnector
[
https://issues.apache.org/jira/browse/ASYNCWEB-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12565961#action_12565961
]
Mike Heath commented on ASYNCWEB-2:
---
I refactored the AHC code to use the
FYI,
I've discovered that this problem is due to a bug with Sun's JRE on Windows:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6230761
I also get this exception on a FreeBSD VMWare running on Windows. However,
it seems to bind fine on Linux, and I'm sure it's okay on Solaris.
Regards,
[
https://issues.apache.org/jira/browse/ASYNCWEB-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12566010#action_12566010
]
Mike Heath commented on ASYNCWEB-2:
---
I renamed SessionCache to ConnectionPool since
30 matches
Mail list logo
