seaside August 2004

seaside@lists.squeakfoundation.org

30 participants
46 discussions

URL parameters and seaside's security
by Kamil Kukura 11 Aug '04

11 Aug '04

I'm thinking about security issue of Seaside. If block which didn't register a callback for it cannot be executed, it makes it pretty secure from attacks such as playing with GET/POST arguments. Of course, there must be care given to values being passed into an application. Btw, when I look to numbers that distinguish links (and input elements and buttons - don't know how do you call them) I see they appear in anchor's HREF in various order. Sometimes the number appears before "_s=...&_k=...", sometimes after and sometimes in the middle. Why is that? -- Kamil

2 4

request termination
by Avi Bryant 10 Aug '04

10 Aug '04

Here's something I'd like an opinion on: if the browser times out when waiting for a response, or the user hits the stop button, and the connection is dropped, Seaside still keeps chugging away on the request. Should we terminate the process instead? And if so, how do we get a notification from the webserver about the dropped connection in a portable way? At least in Squeak, terminating the process does make sure to run all the #ensure: blocks, and I expect/hope the same would be true in other dialects as well. So as long as people are careful, it shouldn't do *too* much damage to kill the process. It's also unlikely that the callback processing is what would take too long and timeout (barring an inifinite loop) - usually it would be the render phase getting terminated, which should be pretty harmless. A

3 3

GOODS tutorial questions
by LK 10 Aug '04

10 Aug '04

As I try to understand the GOODS authentication tutorial, several questions come to mind. 1. Do I need to create a unique 'user' class with #login and #password methods. 2. Is this method usable for all GOODS access, or just for a Login type of situation? withEscapeContinuation: aBlock ^ (self db) commitWithRetry: [super withEscapeContinuation: aBlock] 3. If I want to access several GOODS objects in the same session, I would add more session variables: ie. 'User', 'Logs', 'LogTypes' etc. Thanks for you patience. -Larry

3 2

Menu building pattern?
by C. David Shaffer 04 Aug '04

04 Aug '04

I have been working on a generic menu component and I'm stumbling on managing children. What I'd like to do is after callback processing is complete (and the component tree is finalized for the next rendering pass), traverse the tree and ask each visible presenter for its menu items. The menu items themselves are components so they have to appear in the menu's response to #children during the next render loop iteration. I've made several false starts and I'm getting myself confused. One thing that I thought might work was to change my menu into a decoration of the root component and then to have it override WAPresenter>>processCallbackStream: as such processCallbackStream: aCallbackStream super processCallbackStream: aCallbackStream. self rebuild where rebuild just uses "owner visiblePresentersDo: " to walk the presenter list and build the menu items. I end up with unprocessed callbacks whenever I trigger the menu items' links. Am I thinking about the order of things correctly here? Anyone doing anything like this? David

3 6

2.5b2
by Avi Bryant 04 Aug '04

04 Aug '04

Hi folks, Just released Seaside 2.5b2. The changes from b1, mostly thanks to Adrian Lienhard and Michel Bany, are: - added #orderedList: and #orderedList:do: to AbstractHtmlBuilder - fixed Application>>name to allow an empty basePath - fixed #findStyles to include the request in the context - fixed #valueInputOfType:value:callback: to use the raw string instead of throwing an error when it is expecting a number in the callback but doesn't find one - added a 'Cache-Control: No-cache' header to rendered pages by default I've also been experimenting some with Javascript's XMLHttpRequest support, and have included a preview of this work. You can read more in this blog post, and see an example in WALiveRequestTest: http://www.cincomsmalltalk.com/userblogs/avi/blogView? showComments=true&entry=3268075684 Like the Canvas work, this is *not* a supported part of Seaside 2.5, but since it's independent of the rest of the code I don't mind keeping the previews in the release. Avi

4 7

Changes in GOODS not showing in browser
by LK 04 Aug '04

04 Aug '04

Thanks for all the support. You guys are the greatest! I now have an app that will add and delete records from a GOODS database. My problem now is they added records are not showing in the PMLogsView when I refresh my browser. The user must close and re-open the browser to see the changes. Is there a way to fix this? -Larry Relevent code is below: PMLogsTask>>renderContentOn: html |db | html cssId: 'banner'. html table: [ html tableRowWith: [ html divNamed: 'title' with: self title. html divNamed: 'subtitle' with: self subtitle. ] ]. html render: pmLogsView. html text: 'testing'. ----- PMLogsView>>renderContentOn: html | | html table: [ html tableRow: [html tableHeading: 'View all Log Entries'; space; space; space.]]. html anchorWithAction: [self call: PMLogAddItem new] text: 'Add'. html attributeAt: 'cellspacing' put: 0; attributeAt: 'cellpadding' put: 5; attributeAt: 'border' put: 2. html table: [ allRecords do: [:i | html tableRow: [ html tableData: [html anchorWithAction: [self delete: i from: db] text: 'Del']. html tableData: i type. html tableData: i entryDate. html tableData: i startTime. html tableData: i entryText. html tableData: i endTime. ]. ]. html tableRow: [] ] ----------- PMLogAddItem>>renderContentOn: html " show add new log form" item := PMLogItem new. item initialize. html form: [ html table: [ html tableRow: [html tableHeading: 'New Log Entry']. html tableRow: [html tableData: 'Date'. html tableData: item entryDate]. html tableRow: [html tableData: 'Time'. html tableData: item startTime]. html tableRow: [html tableData: 'Type'. html tableData: [html selectFromList: #('DRE' 'SA' 'DBA' 'TEST') selected: (item type) callback: [:i | item type: i]]]. html tableRow: [html tableData: 'Entry Text'. html tableData: [ html textAreaWithValue: 'log entry' callback: [:i| item entryText: i]]]. ]. html submitButtonWithAction: [self add: item] text: 'Save'. ] --------- PMLogAddItem>>add: aRecord db _ PMDatabase new connect. self table: (db root at: 'logs'). table add: aRecord. db commit. db flush. db logout. self answer. -----

3 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

seaside August 2004