RE: Jasper performance
Velocity does do a lot to minimize the risk you mention, but while we're using stupid coding tricks, couldn't you do the following in Velocity? #* assume strings is a Vector *# #set ($strings = $request.getParameter(strings))) #foreach ($string in $strings) $strings.addElement($string.clone()); #end -Original Message- From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]] Sent: Friday, May 18, 2001 8:50 AM To: [EMAIL PROTECTED] Subject: Re: Jasper performance Dennis Doubleday wrote: At 07:51 AM 5/18/01, Geir wrote: Those aren't comparable, 'Velocity templates' and 'general purpose servlet container', because Velocity is just a template tool - you still need the servlet and servlet container. That was exactly my point when I said Velocity doesn't really do anything to prevent DOS attacks, either. Any Velocity app requires a servlet back-end, and if I'm going to host user apps, I'm going to have to let them install servlets, in which case they can put in the same ever-looping code. Definitely. Agreed. There is no silver bullet. I guess the point is that you remove a little of the risk, as a designer can't % while(true); % (although as JSP compilers get better, I am sure this stuff can be found and flagged...) This is not intended to disparage designers : it's just a different talent set. My use of color has been described as dangerous, bordering on criminal :) geir -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting Developing for the web? See http://jakarta.apache.org/velocity/ still climbing up to the shoulders...
RE: Jasper performance
It isn't concurrent. -Original Message- From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]] Sent: Friday, May 18, 2001 10:52 AM To: [EMAIL PROTECTED] Subject: Re: Jasper performance Jef Newsom wrote: Velocity does do a lot to minimize the risk you mention, but while we're using stupid coding tricks, couldn't you do the following in Velocity? #* assume strings is a Vector *# #set ($strings = $request.getParameter(strings))) #foreach ($string in $strings) $strings.addElement($string.clone()); #end Good try :) Assuming it is a Vector, I am pretty convinced that wouldn't work because you will get a ConcurrentModificationException when you modified the Vector. geir -Original Message- From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]] Sent: Friday, May 18, 2001 8:50 AM To: [EMAIL PROTECTED] Subject: Re: Jasper performance Dennis Doubleday wrote: At 07:51 AM 5/18/01, Geir wrote: Those aren't comparable, 'Velocity templates' and 'general purpose servlet container', because Velocity is just a template tool - you still need the servlet and servlet container. That was exactly my point when I said Velocity doesn't really do anything to prevent DOS attacks, either. Any Velocity app requires a servlet back-end, and if I'm going to host user apps, I'm going to have to let them install servlets, in which case they can put in the same ever-looping code. Definitely. Agreed. There is no silver bullet. I guess the point is that you remove a little of the risk, as a designer can't % while(true); % (although as JSP compilers get better, I am sure this stuff can be found and flagged...) This is not intended to disparage designers : it's just a different talent set. My use of color has been described as dangerous, bordering on criminal :) geir -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting Developing for the web? See http://jakarta.apache.org/velocity/ still climbing up to the shoulders... -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting Developing for the web? See http://jakarta.apache.org/velocity/ still climbing up to the shoulders...
RE: Jasper performance
I wrote a test script, and assuming (which the docs say it does) that Velocity uses the iterator() instead of elements() when it runs up against a vector, then all is well. If elements() is used, it goes into infinite loop land. My mistake. -Original Message- From: Jef Newsom Sent: Friday, May 18, 2001 11:44 AM To: [EMAIL PROTECTED] Subject: RE: Jasper performance It isn't concurrent. -Original Message- From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]] Sent: Friday, May 18, 2001 10:52 AM To: [EMAIL PROTECTED] Subject: Re: Jasper performance Jef Newsom wrote: Velocity does do a lot to minimize the risk you mention, but while we're using stupid coding tricks, couldn't you do the following in Velocity? #* assume strings is a Vector *# #set ($strings = $request.getParameter(strings))) #foreach ($string in $strings) $strings.addElement($string.clone()); #end Good try :) Assuming it is a Vector, I am pretty convinced that wouldn't work because you will get a ConcurrentModificationException when you modified the Vector. geir -Original Message- From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]] Sent: Friday, May 18, 2001 8:50 AM To: [EMAIL PROTECTED] Subject: Re: Jasper performance Dennis Doubleday wrote: At 07:51 AM 5/18/01, Geir wrote: Those aren't comparable, 'Velocity templates' and 'general purpose servlet container', because Velocity is just a template tool - you still need the servlet and servlet container. That was exactly my point when I said Velocity doesn't really do anything to prevent DOS attacks, either. Any Velocity app requires a servlet back-end, and if I'm going to host user apps, I'm going to have to let them install servlets, in which case they can put in the same ever-looping code. Definitely. Agreed. There is no silver bullet. I guess the point is that you remove a little of the risk, as a designer can't % while(true); % (although as JSP compilers get better, I am sure this stuff can be found and flagged...) This is not intended to disparage designers : it's just a different talent set. My use of color has been described as dangerous, bordering on criminal :) geir -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting Developing for the web? See http://jakarta.apache.org/velocity/ still climbing up to the shoulders... -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting Developing for the web? See http://jakarta.apache.org/velocity/ still climbing up to the shoulders...
RE: An alternative to JSP
I have used Excelon Stylus for creating xsl. Although you do a lot of stuff by hand, I found it to be useful for wysiwyg development. I only used it for a short time, so caveat emptor. Too bad it isn't integrated with Dreamweaver. Also too bad that you have to download their portal server to get the eval. $199 per license (blech)... luckily, we're all rich, right? Jef -Original Message- From: Kyle F. Downey [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 11, 2001 1:35 PM To: Paul Libbrecht Cc: [EMAIL PROTECTED] Subject: Re: An alternative to JSP On Thursday, January 11, 2001, at 06:38 PM, Kyle F. Downey wrote: Our chosen solution is to generate XML and style it with XSL. The only thing missing from that picture is a really solid XSL designer integrated with a well-known editor like Dreamweaver. Given that, your designers can How did you solve this trouble then ?? We haven't. We're still writing XSL by hand, along with almost everyone else. Unless such a designer tool is EXTREMELY INTELLIGENT, meaning it makes some reasoning about the way xml elements are placed on an HTML page, or, of course, if your xml content is reasonably static (say two dimensional like an SQL database result-set) then you have the chance to see such a tool, otherwise, I don't view this as a possible thing... I think the solution will look a lot like Allaire Cold Fusion Studio when it comes: a mixture of a solid design tool with a "developer" copy of a rendering engine (Cold Fusion in Allaire's case; an XML app server in this case). That way the designer can get immediate feedback on what the data + view looks like. I agree with you that this is much thornier than simple HTML design, but I think it can be done. --kd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
