>> My boss, who doesn't really know or understand anything about web applications, has decided to save some money on a JSP/Java web application that we have developed as an intranet site, by setting up the site to run as an internet site, but using Citrix to make it available to people outside the company. <<
hahahahaha... First of all, that's the dumbest idea I've ever heard. :) Your users all have Internet Explorer installed on their desktops. So he's going to have them use Internet Explorer to access the Citrix client, which will allow them to remotely control another copy of Internet Explorer--this second copy being the one that resides on your network--which will then make requests to your web application. This, instead of simply having the first copy of Internet Explorer make requests to your web application!!! IE => Citrix => IE => webapp IE => webapp Which do you think will have the lower TCO? Which you do you think will have lower latencies? Which will provide the better user experience? Which will not damage your credibility as a (presumably) technology-savvy corporation? (Answer: the second one) If you're really in a pinch, why not move your web server outside the firewall and just secure your private webapps using other means (which you'd have to do anyway, even in the ridiculous Citrix scenario). -jmc =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
