seaside November 2016

seaside@lists.squeakfoundation.org

16 participants
15 discussions

isolate
by recursive68＠gmail.com 26 Nov '19

26 Nov '19

Hi, Given it looks like the isolate method is never going to added back to the current or future versions of Seaside as it's been an open bug issue for the last 5 years, how in general would go about replicating it's behaviour ? I think it's a shame as I think this sort of functionality made Seaside standout from the crowd as a web framework. Thanks

4 5

Seaside 3.2.0 final
by Johan Brichau 16 Aug '17

16 Aug '17

Hi everyone, Seaside 3.2.0 is now final: https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog <https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog> Check out the Github pages for more information: - https://github.com/SeasideSt/Seaside <https://github.com/SeasideSt/Seaside> - https://github.com/SeasideSt/Seaside/wiki <https://github.com/SeasideSt/Seaside/wiki> If you experience issues, do not hesitate to report an issue via Github. Special thanks goes to all those who have helped, tested or contributed in some other way!

14 26

JQAjax>>#script: in GemStone 3.3.1 with Seaside 3.2.1 works differently than in pharo
by PAUL DEBRUICKER 27 Mar '17

27 Mar '17

In Pharo I can use a #script: send like this html jQuery ajax callback: [ :json | self setMapBoundsFrom: json ] json: (JSStream on: 'map.getBounds()'); script: [ :s | s << ((s jQuery id: #'results') html: [ :r | self renderResultsOn: r ]) ] And the #results id has its content set to the value of the #renderResultsOn: method. In GemStone it seems like a page refresh is happening instead. Has anyone else seen this? I think it was happening in older versions too but I am not sure of what version combination.

3 4

How to configure session timeouts (age)
by Petr Fischer 30 Nov '16

30 Nov '16

Hello, when starting my image with Seaside app, I have this code in startup method: ----- WAMySeasideApp>>startUp: resuming WAMySeasideApp waApplication preferenceAt: #maximumRelativeAge put: 18000. "5 hours" WAEFTTasksApp waApplication preferenceAt: #maximumAbsoluteAge put: 86400. "24 hours" ZnZincServerAdaptor startOn: 8080. WAMySeasideApp>>waApplication ^ WAAdmin defaultDispatcher handlerAt: 'my-seaside-app' ----- This "maximum age" session parameters are correctly showing in seaside config web app, but every seaside session is still 30 minutes. What is proper way to configure session timeouts (age), dynamically, via code? Thanks, pf

6 12

Seaside function onLoad problematic
by dtrussardi＠tiscali.it 28 Nov '16

28 Nov '16

Ciao, into Pharo5.0 with Seaside 3.2 ( but i have the same problematic into Pharo 4.0 with Seaside 3.1 ) when define a function to load when the page has finished loading with addLoadScript: 'so_initdtr()'. the function is not called. For example: renderContentOn: html html document addLoadScript: 'so_initdtr()'. html heading: 'Pippo'. The html report: <script type="text/javascript">function onLoad(){"soinitdtr()";};</script> but the browser don't call it when load the page. The relative javascript code is right loaded into the browser. I can call the so_initdtr() function with the browser console and it works fine. Thanks in advance! Dario

3 5

Seaside - how to render a pre-bult html page
by David Pennington 25 Nov '16

25 Nov '16

Hi there.I have a complex web site that is built using Adobe Muse. I need to add a page to the site that is written using Instantiations VisualAge/Seaside 8.6.2. This is running on Windows Server 2008. I need to load the page into memory, add some specific data to the page and then render it so that it looks and feels like the Muse web site. When the new element is selected (button press) I need to go back to Seaside, process the click and route to another Muse web page using standard http. I don't know how to render an prebuilt html page in Seaside. Is there a way please. Long Haired DavidA.K.A. David Penningtonlhdavid(a)icloud.com Message sent using Winmail Mail Server

5 4

500 - Internal Server Error
by dtrussardi＠tiscali.it 24 Nov '16

24 Nov '16

Ciao, ( I try to report my problematic on this wiki, but I'm not sure ) i'm development Seaside 3.1.4.2 application into Pharo4.0 image Latest update: #40625 Into Pharo i configurate the Server with: Type: ZnZincServerAdaptor Port: 8888 Encoding: utf-8 zinc on port 8888 [running] On the system ( MacBook OS X 10.7.5 ) i configured the Lighttpd web server for redirect the web request to the Pharo server. All works fine but sometimes, when i submit request from the web browser, the system answer: 500 - Internal Server Error When this error happens the lighttpd error.log file report at the same time : 2016-11-18 11:13:53: (network_writev.c.115) writev failed: Socket is not connected 9 2016-11-18 11:13:53: (mod_proxy.c.853) write failed: Socket is not connected 57 2016-11-18 11:13:53: (mod_proxy.c.939) proxy-server disabled: 127.0.0.1 8888 9 2016-11-18 11:13:53: (mod_proxy.c.1316) no proxy-handler found for: /management 2016-11-18 11:13:58: (mod_proxy.c.1361) proxy - re-enabled: 127.0.0.1 8888 Some considerations? The same problematic, but with less frequently, is on Ubuntu server with Gemstone 3.1.0.6 and Seaside 3.0.1.3 On this system the lighttpd error.log file report at the error time: 2016-11-16 18:41:32: (mod_fastcgi.c.2540) unexpected end-of-file (perhaps the fastcgi process died): pid: 0 socket: tcp:127.0.0.1:9061 2016-11-16 18:41:32: (mod_fastcgi.c.3326) response not received, request sent: 1185 on socket: tcp:127.0.0.1:9061 for /management?_s=dHAnR5J1xJNZPC-0&_k=0zNcd6_tcDCkQySv, closing connection The gemstone_status on the server report: Status Version Owner Pid Port Started Type Name ------- --------- --------- ----- ----- ------------ ------ ---- OK 3.1.0.6 scandella 2030 48678 mar 09 23:14 Stone gestionale OK 3.1.0.6 scandella 2032 51188 mar 09 23:14 cache gestionale~9af495ccd1149d82 OK 3.1.0.6 scandella 1041 55320 lug 27 16:42 Netldi gs64ldi /etc/service/gs_maintenance: up (pid 2096) 21900151 seconds /etc/service/gs_seaside-9060: up (pid 2098) 21900151 seconds /etc/service/gs_seaside-9061: up (pid 2100) 21900151 seconds /etc/service/gs_seaside-9062: up (pid 2107) 21900151 seconds /etc/service/gs_seaside-9063: up (pid 25194) 12810073 seconds /etc/service/gs_seaside-9064: up (pid 2111) 21900151 seconds /etc/service/gs_seaside-9065: up (pid 2113) 21900151 seconds /etc/service/gs_statmon-1: up (pid 2069) 21900151 seconds /etc/service/gs_statmon-60: up (pid 2071) 21900151 seconds Thanks for considerations. Dario

2 5

Apache Load Balancing with Seaside
by jtuchel＠objektfabrik.de 14 Nov '16

14 Nov '16

Hi there, we're finally at a stage where we need load balancing is not only needed but also needs to be a bit more fine-grained. So far, we've used Apache's mod_proxy_balancer with an byrequests balancing scheme and the simply Set Cookie, but this is not really distributing load in an even manner, because it simply does a round robin based on requests. Teh way I seem to understand this, this just sends every nth request to another backend, unless the sticky session cookie is there. This seems to have multiple problems in the context of Seaside: 1. each page render consits of dozens of requests, and at least 2 in case of the usual redirect/render cycle 2. So request != new seaside session and therefor not a good base for distribting load 3. It seems the Cokie as marker for stickyness is browser wide. Every new session started in teh same browser gets directed to the same seaside image So this starts to cause problems in our scenario because there is always one image (the first one in the http.conf) that handles most of the load, no matter how many images we add. I think I understand that URL encoding for the load balancer would fit much better for Seaside. What's even better is the fact that Seaside already uses the _s parameter to identify a session. So at first sight, I think it might be a good idea to use the _s parameter provided by Seaside as the URL parameter that is also used for session stickyness. This brings up a few questions: * Is this a good idea? * Has anybody tried? * How to configure this? The most important question, however, is this: would this be any better wrt workload distribution? I mean, how could we make sure the very first request gets redirected to a new image? My fear is that in the end this will still have the same problem: the initial sessions will still be mostly created by the same image all of the time. The only difference might finally just be the fact that we use URL parameters instead of Cookies and spend nights testing and stuff and end up with the same problems... Before you suggest using squid or the like, let's think about the basic problem: does squid do things differently? What mechanism there is so much better than counting requests, measuring bytes transferrred or such? So how do people solve this problem? Any ideas, hints, experiences are greatly appreciated Joachim -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1

3 4

QCMagritte + Material Design Light?
by PAUL DEBRUICKER 14 Nov '16

14 Nov '16

Does anyone have any classes for using MDL instead of Bootstrap? Thanks Paul

1 0

html jQuery ajax 400 Bad Request - solved
by PAUL DEBRUICKER 13 Nov '16

13 Nov '16

Hi - I just spent a little over an hour or so trying to figure out why a JQAjax>>#callback:json: was resulting in a 400 Bad Request error. The error occurred because the JSON body was to long to send in a GET request. When I switched from html jQuery ajax callback:[:json | self processJson: json] json: (JSStream on: 'myInterestingVariable') to html jQuery post callback:[:json | self processJson: json] json: (JSStream on: 'myInterestingVariable') everything worked out great because POST body sizes are allowed to be longer, and that length is set by the server, not the spec. So I'm just sending this note to my future self for the next time I forget this is how the world is. Please forgive the noise. Paul

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside November 2016