check out GNU httptunnel, see if you can compile it to run as a java applet inside a browser, the other end can stay the same since it can run on the server. also, maybe there are already some implementations on the libraries that are ready for use, search sourceforge.
http://www.nocrew.org/software/httptunnel.html * - * - * Tzahi Fadida [EMAIL PROTECTED] Technion Email: [EMAIL PROTECTED] My Cool Site: HTTP://WWW.My2Nis.Com * - * - * - * - * - * - * - * - * - * WARNING TO SPAMMERS: see at http://members.lycos.co.uk/my2nis/spamwarning.html > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Eli Marmor > Sent: Wednesday, October 30, 2002 9:33 AM > To: Linux-IL mailing list > Subject: Re: upcoming java ssh2? > > > Tzafrir Cohen wrote: > > > > >From the creators of WeirdX: > > > > http://www.jcraft.com/jsch/ > > > > version 0.0.6 of a java implementation of ssh2 > > I think it's great that these people port to Java applets any > client of > any client-server protocol (X, SSH, etc.) > > But there is still something that concerns me: It is known to any Java > professional that the ideal protocol for Java applets (to communicate > with a remote server) is HTTP (or HTTPS). SOAP was invented for this > purpose. Web services are based on this rule. Even ICQ ships such an > applet > > The reason: Contrary to typical client-server sessions (which are used > typically in LAN's and Intranets), Java applets are used by > "far" users > who connect to the server from the Internet; You don't have any idea > where do they come from, what routers and firewalls they had to pass, > etc > > Yes, the backend servers still use non-HTTP protocols, but this is > usually resolved by servers (or should I say proxies) that are put in > the middle, access the backends as "clients", while serving those > applets as "HTTP servers". Usually, these servers are even a part of > the backend (so the backend serves both - its own original protocol, > AND HTTP) > > Sometimes, all these proxies have to do is to "tunnel" the original > protocol through HTTP/HTTPS > > > So the big question: Why, when it comes to important protocols such as > SSH, X, IRC, VNC, etc., the applets must speak those > protocols directly > with the backend, and can't speak it over HTTP/HTTPS? > > Or it's possible? If yes, then how? > > -- > Eli Marmor > [EMAIL PROTECTED] > CTO, Founder > Netmask (El-Mar) Internet Technologies Ltd > __________________________________________________________ > Tel.: +972-9-766-1020 8 Yad-Harutzim St > Fax.: +972-9-766-1314 P.O.B. 7004 > Mobile: +972-50-23-7338 Kfar-Saba 44641, Israel > > ================================================================= > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] > > > > ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
