hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jørgen Nordmoen (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (HTTPCORE-295) Change Traffic class of an established connection
Date Wed, 07 Mar 2012 17:30:57 GMT

    [ https://issues.apache.org/jira/browse/HTTPCORE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224526#comment-13224526

Jørgen Nordmoen commented on HTTPCORE-295:

Hi again Oleg :)

Having access to the socket is one solution, but as you pointed out that is not very elegant.
Although for our needs exposing the underlying socket would work just as well. 

I suggest we(meaning me and my group) have a look at SSLIOSession and try to understand how
it works and how the decoration work then create a new patch with the pattern you suggested
which you could review again.

Thanks for the helpfull reply.
- Jørgen Nordmoen
> Change Traffic class of an established connection
> -------------------------------------------------
>                 Key: HTTPCORE-295
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-295
>             Project: HttpComponents HttpCore
>          Issue Type: Improvement
>          Components: HttpCore NIO
>    Affects Versions: 4.1.3, 4.2-beta1
>            Reporter: Jørgen Nordmoen
>            Priority: Minor
>         Attachments: hc.diff
> Request:
> Currently there is no possibility of changing the traffic class in HTTPCore, this could
be fixed by exposing the methods setTrafficClass(int) and getTrafficClass() in http://docs.oracle.com/javase/7/docs/api/java/net/Socket.html.
This can already be done with setSocketTimeout(int), and there is also a feature request for
doing it with setTcpNoDelay() and setSocketKeepalive() (https://issues.apache.org/jira/browse/HTTPCORE-288).
> Motivation:
> Supporting traffic class could be quite beneficial for HTTPComponents as it allows projects
depending on HC to control the quality of service. This could be used by e.g. Apache Synapse
to give outgoing request or replies different QoS parameters depending on the client connecting
to the service.
> Problems:
> As I'm not familiar enough with HTTPCore I can't give a precise suggestion here, but
just by guessing the same issues put forward by this issue: https://issues.apache.org/jira/browse/HTTPCORE-288
might effect this request to.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

View raw message