[Seaside Issues] Issue 742 in seaside: Generated javascripts are not directly serialized on the canvas stream (leading to slow performance?)

seaside at googlecode.com seaside at googlecode.com
Sat Sep 1 15:49:55 CEST 2012


Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 742 by jo... at yesplan.be: Generated javascripts are not directly  
serialized on the canvas stream (leading to slow performance?)
http://code.google.com/p/seaside/issues/detail?id=742

I observed a very slow response when generating a lot of javascripts. The  
bulk of the time was spent serializing the response (so outside of the  
renderContentOn: control-flow - and 2 to 3 times more time).

I essentially solved my problem by using event delegation (with jQuery's  
on:do:) but when talking to Philippe, he pointed towards the fact that the  
javascript objects are not serialized directly on the canvas stream. The  
culprit probably has something to do with the #greaseString in the method  
below.

WAScriptGenerator>>writeLoadScriptsOn: aDocument
	"Utitlity method to write the receivers load scripts onto aDocument."

	self loadScripts do: [ :each |
		aDocument nextPutAll: each greaseString; nextPut: $; ]




More information about the issues mailing list