seaside May 2019

seaside@lists.squeakfoundation.org

13 participants
10 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

Front-End developer coordination
by BrunoBB 28 May '19

28 May '19

Hi, We are doing a project with Seaside and there is a Front-end developer mostly for CSS creation. How do you approach this problem (coordination between Seaside developer and frontend developer) ? I mean in Seaside the HTML code is generated but it has to do some references to the CSS created by the frontend developer. One approach can be: 1) Add css class names (the css does no exist yet) in Seaside code (html div class: 'to-be-developed-by-frontend-dev'). 2) The frontend create the CSS file for classes in 1). Very simple but i wonder how do you solved this problem ? regards, bruno -- Sent from: http://forum.world.st/Seaside-General-f86180.html

9 13

WAApplication and WASession subclassing and expiry, again
by Tim Johnson 25 May '19

25 May '19

Hi, The current recommended practice seems to be to subclass WAApplication[1][5][6] especially if one wants to handle session expiration/expiry[2]. One must then register the WAApplication as the application root, and use other tricks (override another method) to get one's component (or task) into the flow [3], it seems. I am a student of the HPI book[4] (since many years ago) which trains me to keep all of my application logic (model) in my custom WASession subclass. If I am to also subclass WAApplication, am I to move all of my application logic to that instead[7]? I ask because I am recently dealing with the first Seaside app I have deployed to the wider internet (instead of an intranet), and sessions are not expiring, a'la [4]. They will stick around for days. My app also seems to lock up after about 24 hours which is getting annoying. :) When I look at implementors and senders of #unregistered[8], I see that perhaps I should now be subclassing WAExpirySession instead of WASession if I want my sessions to expire (or if I want to hook into the expiration process)...? I cannot find much documentation on the net regarding WAExpirySession. Also, I am on Seaside 3.2.2 — might it help to upgrade? Thanks, Tim [1] https://github.com/SeasideSt/Seaside/issues/1113 [2] http://www.seaside.st/documentation/faq/how-to#254979024 [3] https://kentreis.wordpress.com/2008/01/22/ <https://kentreis.wordpress.com/2008/01/22/> [4] http://forum.world.st/Seaside-sessions-not-being-either-unregistered-or-GCe… [5] https://stackoverflow.com/questions/43824202/catching-the-session-expiry-in… [6] https://stackoverflow.com/questions/41173162/how-to-configure-seaside-3-2-s… [7] http://forum.world.st/Subclass-WAApplication-td98970.html [8] http://forum.world.st/Sharing-Seaside-URLs-between-users-security-what-is-a…

2 2

Uptime in WAImageStatus
by Tim Johnson 23 May '19

23 May '19

Hi, On Squeak, the "Uptime" value in WAImageStatus seems to need adjustment. In Seaside 3.3, my uptime says this: Uptime: 43241 days 14 hrs 53 min 42 sec If I change WAImageStatus>>#renderValuesOn: so that: upTime := Duration milliseconds: Time eventMillisecondClock. it becomes much more realistic: Uptime: 1 day 14 hrs 20 min 43 sec Thanks, Tim J

1 0

Re: [Seaside] [vwnc] Managing Large File Uploads in Seaside
by Esteban Maringolo 09 May '19

09 May '19

Overrides are a door to abuse and sometimes an indicator or a bad design, IMO, but as with other powerful tool, it depends on each case. What I don't like the pragma based configuration of this part, the whole senders/implementors and class references of Smalltalk are not of much use there, since it is hard to find where things are defined, configured, etc. E.g. SeasideResponder class>>#configureCurrent Regards, Esteban A. Maringolo On Wed, May 8, 2019 at 2:54 PM Tom Robinson <zxrobinson(a)gmail.com> wrote: > Hi Karsten, > > This appears to be a common issue. As such, rather than just using an > override, maybe Cincom should be asked for an implementation change that > would ALLOW subclasses to customize this without too much code duplication. > In my opinion, if an override is needed, in most cases it indicates that > more flexibility in the original implementation is needed. > > Tom > > On 5/8/2019 11:30 AM, Karsten Kusche wrote: > > What do you mean by body size limit? Is that a http thing? > > As for subclassing, the method in question isn’t written in a way that > would allow subclasses to customize something without copying too much > code. In that case an override is better, because there’s tool support to > find overrides and inspect them upon migration. > > Karsten > > > > > Am 8. Mai 2019 um 19:23:15 MESZ schrieb Esteban Maringolo > <emaringolo(a)gmail.com> <emaringolo(a)gmail.com>: > > Hi Karsten, > > I didn't think about an override and went subclassing directly (I'm not > keen/not used to method overrides), but your approach of having a threshold > seems like a good tradeoff to preserve the simplicity for small files. > > What I couldn't find is whether the maximum request body size is enforced > with Seaside (I placed a few breakpoints around senders of > #requestBodyLimit without any luck). > > Regards, > > Esteban A. Maringolo > > > On Wed, May 8, 2019 at 1:59 PM Karsten Kusche <karsten(a)heeg.de> wrote: > > Hi Esteban, > > we have an override in SeasideResponder>>asSeasideFileStream: where we do > something differently in „stream isExternalStream ifTrue:[…]“ > > There we ask the stream for #fileName (returns a Filename object) and test > the file size. That’s the file that contains the data that was uploaded. If > the file’s size exceeds a certain threshold we return a subclass of WAFile > that knows the file and not its contents. > > Kind Regards > Karsten > > Georg Heeg eK > > Wallstraße 22 > > 06366 Köthen > > > > Tel.: 03496/214328 > > FAX: 03496/214712 > > Amtsgericht Dortmund HRA 12812 > > > Am 8. Mai 2019 um 16:29:29, Esteban Maringolo (emaringolo(a)gmail.com) > schrieb: > > I found that SiouX is effectively uploading the contents to an attachment > file directory. > > Maybe there is a way to avoid instantiating a WAFile and use a > WAExternalFile poiting to the file on disk, or simply using my custom > SeasideResponder subclass. > > This won't save VW from reading the whole file into memory before saving > it to disk (or will it?) but it certainly will only keep the reference > during the request/response of SiouX, which will be garbage collected > faster than anything on a Seaside Component. > > Regards, > > Esteban A. Maringolo > > > On Wed, May 8, 2019 at 10:10 AM Esteban Maringolo <emaringolo(a)gmail.com> > wrote: > > Hi Felix, > > That is similar to what Johan proposes in his article, but the goal is to > achieve the same thing by using SiouX (VW's latest HTTP server) responders, > maybe using a chunked read/write approach (so there is no more than a > certain buffer in the object memory). > > Regards, > > Esteban A. Maringolo > > > On Wed, May 8, 2019 at 9:46 AM Félix Madrid <fmadrid(a)gmail.com> wrote: > > Hi Esteban, > > Maybe this article (and project) from Nick Ager can help you: > > http://nickager.com/blog/2011/07/01/File-upload-using-Nginx-and-Seaside > <https://urldefense.proofpoint.com/v2/url?u=http-3A__nickager.com_blog_2011_…> > > Cheers, > > Félix > > On Wed, May 8, 2019 at 2:39 PM Esteban Maringolo <emaringolo(a)gmail.com> > wrote: > > I'm trying to use the SiouX responder fortification to limit a large file > upload from blocking the whole image and/or filling its memory. > > Looking at the options I found there is a "save attachments as files", > which seems like a similar approach as the one proposed at < > https://jbrichau.github.io/blog/large-file-upload-in-seaside > <https://urldefense.proofpoint.com/v2/url?u=https-3A__jbrichau.github.io_blo…> > > using NGINX or Apache, but apparently that option only works at > NetHttpResponder, but it's not applied in Seaside. > > Did anybody integrate this feature or a similar one with Seaside in VW? > (otherwise I'd have to do it myself). > > Regards! > > Esteban A. Maringolo > > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.squeakfoundation.…> > > >

2 2

Re: [Seaside] [vwnc] Managing Large File Uploads in Seaside
by Esteban Maringolo 08 May '19

08 May '19

Hi Felix, That is similar to what Johan proposes in his article, but the goal is to achieve the same thing by using SiouX (VW's latest HTTP server) responders, maybe using a chunked read/write approach (so there is no more than a certain buffer in the object memory). Regards, Esteban A. Maringolo On Wed, May 8, 2019 at 9:46 AM Félix Madrid <fmadrid(a)gmail.com> wrote: > Hi Esteban, > > Maybe this article (and project) from Nick Ager can help you: > > http://nickager.com/blog/2011/07/01/File-upload-using-Nginx-and-Seaside > > Cheers, > > Félix > > On Wed, May 8, 2019 at 2:39 PM Esteban Maringolo <emaringolo(a)gmail.com> > wrote: > >> I'm trying to use the SiouX responder fortification to limit a large file >> upload from blocking the whole image and/or filling its memory. >> >> Looking at the options I found there is a "save attachments as files", >> which seems like a similar approach as the one proposed at < >> https://jbrichau.github.io/blog/large-file-upload-in-seaside > using >> NGINX or Apache, but apparently that option only works at NetHttpResponder, >> but it's not applied in Seaside. >> >> Did anybody integrate this feature or a similar one with Seaside in VW? >> (otherwise I'd have to do it myself). >> >> Regards! >> >> Esteban A. Maringolo >> > >

2 5

Managing Large File Uploads in Seaside
by Esteban Maringolo 08 May '19

08 May '19

I'm trying to use the SiouX responder fortification to limit a large file upload from blocking the whole image and/or filling its memory. Looking at the options I found there is a "save attachments as files", which seems like a similar approach as the one proposed at < https://jbrichau.github.io/blog/large-file-upload-in-seaside > using NGINX or Apache, but apparently that option only works at NetHttpResponder, but it's not applied in Seaside. Did anybody integrate this feature or a similar one with Seaside in VW? (otherwise I'd have to do it myself). Regards! Esteban A. Maringolo

1 0

AJAX File Uploads
by Esteban Maringolo 07 May '19

07 May '19

I need to upload files and I'd like to be able to do it using AJAX to provide some live feedback. I need it to upload some proprietary binary files (no preview, etc.). Is anybody using a library for this that integrates with the existing callbacks in a similar fashion as jQuery's `serializeThis` or `serializeForm`? Regards, Esteban A. Maringolo

1 1

any jquery mobile users? - there is an XSS vuln that might get announced in the next few days
by PAUL DEBRUICKER 03 May '19

03 May '19

https://github.com/jquery/jquery-mobile/issues/8640 Evidently jQuery doesn't have devs to assign to fix it and it affects all versions. So the recommendation is to port to something else. If it is true and is released and is not fixed should we pull the jQuery mobile integration in Seaside?

1 0

Updating browser history from an ajax response
by Esteban Maringolo 01 May '19

01 May '19

I have a Seaside application that is almost 100% AJAX driven to replace the visual components (no call/answer involved). I plan to to use history.pushState() and history.replaceState() My plan is to update the browser url after replacing some components, but using the URL building of the existing #updateUrl: (including _s/_k parameters and whatnot). Is it possible to obtain the URL of the session presenter within the ajax response? Thanks in advance, Esteban A. Maringolo

5 11

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside May 2019