There are no real limitations. Using Apache as a reverse proxy in front of Restlet should work just fine, actually better than having Restlet answer internet requests directly.
Restlet does tend to be stricter about HTTP header formats than most HTTP servers. Things that Apache's mod_php would handle happily may not be OK with Restlet. But this is a good thing: the internet is a wild place full of bizarre robots, spiders from Mars, and other junk that will start hitting your server almost as soon as you open it to the world... The bottom line is that Restlet is recommended for commercial, internet-public sites. -Tal On 03/24/2011 09:52 AM, Robert P Futrelle wrote: > I work in Java for servers and clients. They all work fine on my local > machine (most of the time ;-). > > Is anyone familiar with the issues (limitations?) that could arise in > attempting to create a java restlet server and then deploying it/them > on a commercial hosting site? > > They all have Apache available, but I'm not familiar enough with web > software architecture to know what can be put behind Apache. > - Bob Futrelle > BioNLP.org > Northeastern University > > > ------------------------------------------------------------------------ > View this message in context: Deploying restlets on a commercial > hosting service? > <http://restlet-discuss.1400322.n2.nabble.com/Deploying-restlets-on-a-commercial-hosting-service-tp6204385p6204385.html> > Sent from the Restlet Discuss mailing list archive > <http://restlet-discuss.1400322.n2.nabble.com/> at Nabble.com. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2713904
