Fyi, Meeh is working on "i2ptunnel"

[meeh420]

Just wanted to give you a heads up that I've started on the "client" part. In other words classes to link i2p::stream::Stream to a configured tcp port. I will commit when I got something, but it might take a while since I need to learn the ASIO library better. Still learning C++ in depth.

My initial design thoughts is close to this, if you change the server with the Stream object. http://www.partow.net/programming/tcpproxy/index.html

[orignal]

I would start from simple HTTP-proxy.
You can see the example how Stream class is used in HTTPServer.cpp. However I would like to implement async operations for Stream, that will let you attach to io_service easily.

[meeh420]

Yea, I've used the example from HTTPServer.cpp on how to query. I don't have any knowledge with io_service so that's something I try to read me up on now. Read some of the code in the link above too, gave me some ideas.

Async would be sweet because then I can do something like this:

m_I2PStream.async_read_some(
                    boost::asio::buffer(m_UpstreamData,max_data_length),
                    boost::bind(&I2PConnection::handleUpstreamRead,
                      shared_from_this(),
                      boost::asio::placeholders::error,
                      boost::asio::placeholders::bytes_transferred));

[orignal]

The bottom line of this design is you would have to allocate separate local port per I2P destination. Remember there are not so many local ports available, 2 bytes only.

[meeh420]

Ah, I see what you mean. Back to design board, need to do it in another way. Thanks.

This desgin would only be useful for IRC,smtp,pop with a static destination, and not HTTP.
Anyhow, I should make it possible to use multiple destinations, like the default IRC proxy.

[orignal]

That's why I'm saying HTTP proxy is simplest because it contains destination address in the headers.

[meeh420]

Ok, I'm going for that one first, then extend or implement for more later.

[meeh420]

Starting to get results. Just wondering, is it an good idea to "cache" leasesets or streams in the HTTP proxy? Thinking of senarioes where you load different files from the same host, seems waste of resource to lookup leaseset and create stream for each request.

What do you think?

[orignal]

As you might see I have implemented LeaseSet subscription mechanism meaning someone who is interested in it subscribes and LeaseSet gets updated automatically.

Why do you think looking up of LeaseSet or creating stream is something resource consuming?
If you mean ElGamal/Tags, that's assigned per destination not per stream.
However using same stream for downloading entire site, like images, frames, etc. would be good idea, but I'm not sure how it's sorted out at another end, as far as I see, it closes socket immediately once transmission end. That means if you receive "close" event you can't reuse same stream but have to establish new one.

[meeh420]

Hi, I sent you an mail to the mail address in your git checkin signature. Was hoping to have a little chat :) - Also, just close this issue when you read this.

[orignal]

Yes, I see you e-mail.