Well Ray there will always be people who will try that, however this is far less likely to cause an issue here because Java is running as a process inside an application pool, not as a service. So if a request takes too long the process gets killed and the application pool recycled just like ASP.net. So it shouldn't cause the same kind of problems that you are used to with Coldfusion where a runaway request just kills JRUN/Tomcat. Give it a try, make a really long loop 1- 1000000 and see what happens.
On Mon, May 20, 2013 at 11:31 AM, Raymond Camden <raymondcam...@gmail.com>wrote: > > I'd still be concerned with code that runs forever, or uses other 'heavy' > calls like lots of cfhttp, etc. > > > On Sun, May 19, 2013 at 10:41 PM, Russ Michaels <r...@michaels.me.uk> > wrote: > > > > > OK I have done a complete rewrite of how it works now. > > All saved code is now executed in a totally difference instance than the > > site itself, so uploaded code no longer has any access to the site files, > > so that avoids all the permissions issues, and that instance is not > > remotely accessible either. plus also has greater Railo access > > restrictions as well. > > > > > > > -- > =========================================================================== > Raymond Camden, Adobe Developer Evangelist > > Email : raymondcam...@gmail.com > Blog : www.raymondcamden.com > Twitter: cfjedimaster > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:355796 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
