Uploaded image for project: 'Netty'
  1. Netty
  2. NETTY-109

Subproject: HTTP Tunnel

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 3.1.0.ALPHA4
    • Component/s: None
    • Labels:
      None

      Description

      JBoss Messaging team proposed to create a generic HTTP tunnel which turns an existing Servlet container to a proxy to an existing Netty application which runs on in-VM or socket transport. A compatible HTTP client, written in Netty, could allow a user to bypass an HTTP friendly firewall and use the HTTP connection just like using a plain socket. This feature could be shared among various network applications that need to work with firewalls (e.g. JBREM and JBM)

      The name of the subproject is Netty HTTP Tunnel (or HTunnel? I think Andy should choose or come up with a better name. , named after stunnel - http://www.stunnel.org/

      HTTP Tunnel should provide the following components:

      (A) An implementation of ClientSocketChannelFactory that implements the compatible HTTP client (i.e. just like using a socket)
      (B) A WAR which turns an existing Servlet container to a proxy to an existing Netty application
      (C) A stand-alone Netty-based HTTP proxy server which is interoperable with (A) - perhaps optional, but should be easy to implement.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ataylor Andy Taylor
                  Reporter:
                  trustin Trustin Lee
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: