On Thu, 28 May 2009, Peter Stuge wrote: >> Or perhaps the question should rather be put: what should we do to libssh2 >> to make this a lot less complicated? > > It's similar to forwarded TCP ports. If libssh2 should take care of > everything it has to manage these connections coming and going. I think just > one forwarded connection of each type would be fine to begin with. > > Or libssh2 can push this task to the application, and only do minimum SSH > protocol. But that doesn't feel quite as warm and fuzzy.
I realize that the actual underlying forwarning mechnism within the SSH protocol is quite complex, but I hadn't understood that this much of that complexity had to be done by the application - shown by the x11.c example. I thought libssh2 would provide more. This said, I'm not sure how libssh2 would offer this "extra" and quite frankly X11/port forwardning is not high on my own personal agenda so I won't persue this much on my own at this point in time. And of course, once we have a cleaned up and streamlined x11.c example, more people can - thanks to Olivier Hervieu - learn from that and we can then look at that example to see what parts of it we could perhaps convert into helper functions within the library. -- / daniel.haxx.se ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ libssh2-devel mailing list libssh2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libssh2-devel
