Hi Sam,
> I'm currently looking to rewrite our (blocking) tunneling software
> using NIO (in an effort to increase scalability), and Grizzly seems
> like it could save me a considerable amount of time. To be clear, this
> is for tunneling arbitrary TCP traffic (not just HTTP!), over both SSL
> and non-SSL.
>
> Having searched the archives, I see that someone else two years was
> interested in something similar
> (https://grizzly.dev.java.net/servlets/ReadMsg?
> listName=users&msgNo=52).
> Are the concepts largely the same nowadays? I know the Grizzly
> libraries have progressed a great deal since then, so I didn't want to
> dive too deeply into that if there were more appropriate ways of
> achieving this these days.
>
> Any other pointers would be most welcome!
IMHO it should be pretty easy to write simple tunneling application.
All you'll need on server side - is to build filter chain and keep
client<->server connection map to redirect data among them.
I've just created simple tunnel example for Grizzly 2.0, hope it will
help.
To build them - please use the latest Grizzly 2.0 snapshot [2]
WBR,
Alexey.
[1]
https://grizzly.dev.java.net/source/browse/grizzly/branches/2dot0/code/samples/framework-samples/src/main/java/com/sun/grizzly/samples/tunnel/
[2]
<groupId>com.sun.grizzly</groupId>
<artifactId>grizzly-framework</artifactId>
<version>2.0.0-SNAPSHOT</version>
>
> Many thanks,
>
> Sam
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>