seaside-dev December 2008

seaside-dev@lists.squeakfoundation.org

11 participants
128 discussions

Issue 263 in seaside: Figure out configuration of filters
by codesite-noreply＠google.com 27 Dec '08

27 Dec '08

Status: Accepted Owner: ---- Labels: Type-Feature Priority-Medium Version-Seaside2.9 New issue 263 by renggli: Figure out configuration of filters http://code.google.com/p/seaside/issues/detail?id=263 Currently it is not possible to configure filters from the web. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 194 in seaside: Implement forward requests
by codesite-noreply＠google.com 27 Dec '08

27 Dec '08

Comment #5 on issue 194 by renggli: Implement forward requests http://code.google.com/p/seaside/issues/detail?id=194 Philippe, could you elaborate what a "forward requests" is? Is it this: "forward() does not involve the client's browser. It just takes browser's current request, and hands it off to another servlet/jsp to handle. The client doesn't know that they're request is being handled by a different servlet/jsp than they originally called." If so, why not just call #handleRequest: on another handler? Why must special care taken for #returnResponse:? On the level of WARequestHandler and WARequestFilter there is no #returnResponse:, these objects just return the response if they finished processing. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 262 in seaside: Creating a new session is O(n)
by codesite-noreply＠google.com 26 Dec '08

26 Dec '08

Comment #1 on issue 262 by ssas...(a)seaswork.com.ar: Creating a new session is O(n) http://code.google.com/p/seaside/issues/detail?id=262 I've observed that images which are not restarted for quite some time (maybe weeks) gets less responsive than fresh recently started up worker images. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 262 in seaside: Creating a new session is O(n)
by codesite-noreply＠google.com 26 Dec '08

26 Dec '08

Status: New Owner: ---- Labels: Type-Feature Priority-Low New issue 262 by philippe.marschall: Creating a new session is O(n) http://code.google.com/p/seaside/issues/detail?id=262 When a new session is created, all sessions are iterated over and checked whether they're still active. This effectively makes creating a new session O(n), where n is the total number of session. In practice the scanning code is executed only for every tenth new session, however this doesn't make it any faster and O(n/10) is still equivalent to O(n). The suggested solution is to additionally have the sessions in a linked list ordered by access time. The session dictionary holds to the node so that upon access in can efficiently be moved to the end of he list. Upon session creating the start of the list is scanned only until a session is encountered who is not yet expired. Additionally a open hashtable can be used to overcome issues with the Squeak closed hashtable (Dictionary). Implementation notes: It should be possible to still have sessions with a custom, higher lifetime. So the abort condition for scanning should be slightly relaxed. Depending on the hashtable package is not an option. If you want this functionality extract the Hashtable class, remove all not needed methods (that should be most of them) and prefix it WA*. Also check if other dialects, they might have Dictionary classes that don't have the same issues as Squeak so they might want to use their own. This might especially be the case for GemStone. http://www.nabble.com/WARegistry-performance-td20995160.html http://www.nabble.com/WARegistry-performance-td21020361.html -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 256 in seaside: Setting the default entry point does not seem to work
by codesite-noreply＠google.com 22 Dec '08

22 Dec '08

Updates: Status: Invalid Owner: renggli Comment #1 on issue 256 by renggli: Setting the default entry point does not seem to work http://code.google.com/p/seaside/issues/detail?id=256 This works as expected in my images. Setting the default entry point is local and only affects the dispatcher that is currently edited, it is not supposed to modify the root path. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 211 in seaside: deprecate the scriptcaulous convenience methods on Canvas
by codesite-noreply＠google.com 22 Dec '08

22 Dec '08

Updates: Status: Fixed Owner: renggli Comment #2 on issue 211 by renggli: deprecate the scriptcaulous convenience methods on Canvas http://code.google.com/p/seaside/issues/detail?id=211 Name: Scriptaculous-Core-lr.64 Author: lr Time: 22 December 2008, 11:47:44 pm UUID: 1b785560-5b5f-4c6d-a90b-8299c4f2c574 Ancestors: Scriptaculous-Core-lr.63 - deprecate the scriptcaulous convenience methods on Canvas and on JSScript - fixes Issue 211 Name: Scriptaculous-Tests-Core-lr.19 Author: lr Time: 22 December 2008, 11:48:20 pm UUID: a6cfd956-9efc-49a7-93a6-ae2d47b7e870 Ancestors: Scriptaculous-Tests-Core-lr.18 - fixes deprecated method calls - fixes Issue 211 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 261 in seaside: undeclareds in Seaside2.8a1-pmm.581.mcz and Scriptaculous-lr.243.mcz
by codesite-noreply＠google.com 20 Dec '08

20 Dec '08

Updates: Status: Fixed Owner: philippe.marschall Comment #1 on issue 261 by philippe.marschall: undeclareds in Seaside2.8a1-pmm.581.mcz and Scriptaculous-lr.243.mcz http://code.google.com/p/seaside/issues/detail?id=261 Name: Seaside2.8a1-pmm.582 Author: pmm Time: 20 December 2008, 3:04:16 pm UUID: b98e44f0-7fce-44c2-8287-75040a719fe1 Ancestors: Seaside2.8a1-pmm.581 - fixed undeclareds Name: Scriptaculous-pmm.244 Author: pmm Time: 20 December 2008, 3:10:07 pm UUID: fc7d1c6e-8198-4296-aef6-de579a013f2b Ancestors: Scriptaculous-lr.243 - added lost instance variable -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

But who will test the tests?
by Julian Fitzell 19 Dec '08

19 Dec '08

> Seaside-Core-jgf.342.mcz > from Seaside 2.9 by James Foster <Squeak.Source(a)JGFoster.net> > Move Integer>>#printStringAsCents and MessageSend>>#numArgs from Seaside-Core to Seaside-Platform so that Platform tests pass without loading Core. I'm excited that you're testing this stuff, James. I keep saying that each of the test packages should run with only the package it is testing and dependencies loaded but nobody has had a chance to try it yet. Julian

2 1

Issue 260 in seaside: Load order problem with tests
by codesite-noreply＠google.com 18 Dec '08

18 Dec '08

Updates: Status: Started Comment #4 on issue 260 by renggli: Load order problem with tests http://code.google.com/p/seaside/issues/detail?id=260 Is #printStringAsCents still needed? THere is just a test sending it. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 234 in seaside: Source code view is broken after painter refactoring
by codesite-noreply＠google.com 18 Dec '08

18 Dec '08

Updates: Status: Duplicate Mergedinto: 245 Comment #1 on issue 234 by obi068: Source code view is broken after painter refactoring http://code.google.com/p/seaside/issues/detail?id=234 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

← Newer
1
2
3
4
5
6
7
...
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

seaside-dev December 2008