#2117 closed enhancement (wontfix)

Connect from i2ptunnel to Jetty internally

Reported by: zzz Owned by:
Priority: minor Milestone: eventually
Component: apps/i2ptunnel Version: 0.9.32
Keywords: Cc:
Parent Tickets:


This will reduce resource usage including FDs for high-traffic Jetty servers (see #2116). We would have to implement (at least) Jetty interfaces Connector, ConnectionFactory?, Connection, and EndPoint?. EndPoint? would be a bridge to our InternalSocket?.

Not easy and maybe not worth it.


Change History (3)

comment:1 Changed 17 months ago by zzz

This would be really helpful for zzzot also. jetty.io.AbstractConnection? and AbstractEndPoint? should make it a lot easier.

comment:2 Changed 17 months ago by zzz

  • Status changed from new to open

Partially working, extending AbstractNetworkConnector? and AbstractEndPoint?. We do not need or want our own versions of Connection and ConnectionFactory?. Big issue is if we can do this efficiently, fit into Jetty's nio scheme while actually doing synch i/o, and save Threads. We'd need to make internal versions of the I2PTunnelRunner and CompressedRequestor? in I2PTunnelHTTPServer. Two threads each, if we can get that down to 1 or zero it's a win; otherwise, let Jetty do its nio thing.

comment:3 Changed 11 months ago by zzz

  • Resolution set to wontfix
  • Status changed from open to closed
Note: See TracTickets for help on using tickets.