[Seaside-dev] Issue 140 in seaside: decide whether WAObject>>session and >>application should return nil if no request context found

codesite-noreply at google.com codesite-noreply at google.com
Fri Sep 12 21:58:01 UTC 2008


Issue 140: decide whether WAObject>>session and >>application should return  
nil if no request context found
http://code.google.com/p/seaside/issues/detail?id=140

Comment #4 by da... at teleport.com:
You had mentioned that you 'didn't think there were many cases where you'd  
want to
allow things to work with no request context' and I wanted to point out that
inspectors will have no request context and objects that depend upon a  
request
context to display themselves would be difficult to inspect as in case #69.  
Therefore
you will want to 'allow things to work with no request context'.

It's annoying when this happens because you are typically trying to debug  
something
totally unrelated and your inspector starts blowing up...testing for nil's  
and moving
on would be marginally easier than dealing with Errors...

Perhaps returning something like a WANullReqestContext (with little or no  
behavior)
would make the problem a little more obvious.



-- 
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


More information about the seaside-dev mailing list