You guys want a Tunnel library that can tunnel RMI over http? http://sebster.com/tunnel/
works fine. We use it in our product So if you want to code a Swing client that sort of is a browser but then a bit fatter and uses http (rmi over htttp or something else) you can do that just fine johan On Thu, Jul 17, 2008 at 10:18 AM, Michael Allan <[EMAIL PROTECTED]> wrote: > Zappaterrini, Larry wrote: > > > > Your reason is a special instance of a much more general reason. Web > > applications are much easier to deal with from a deployment > > perspective than desktop applications. > > I don't know, it's not difficult to set up an RMI server, or to deploy > a Swing client with Web Start (gives the user a single-click launch > from the browser). I've done it, and frankly it's easier than messing > with Tomcat and Web frameworks (no offense to Wicket). > > And any developer who's coded a GUI using a proper toolkit, such as > Swing, will never willingly trade it for a Web framework. (A big part > of the attraction of Wicket is its Swing-like, component design. But > it can't approach the real thing.) > > > Also, there are firewall and security issues surrounding access to > > central data repositories that web applications handle nicely. > > That security coddling is a mixed blessing. The browser's sandbox, > for instance, makes it a complicated business to provide the user with > normal access to resources on the desktop. With Swing, your app is a > full peer on the desktop. > > True, there are firewall and NAT hurdles for RMI clients. I googled > for "RMI over HTTP" and "HTTP tunneling", and I didn't get a > comfortable, reassuring response. Why is that? It's a mystery... It > should be a well beaten path. > > -- > Michael Allan > > Toronto, 647-436-4521 > http://zelea.com/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
