[Seaside-dev] Issue 227 in seaside: #halt should always halt

codesite-noreply at google.com codesite-noreply at google.com
Wed Nov 5 23:41:15 UTC 2008


Issue 227: #halt should always halt
http://code.google.com/p/seaside/issues/detail?id=227

Comment #10 by da... at teleport.com:
Lukas, when you say 'bring up a debugger' do you mean a Squeak debugger or  
a Seaside
debugger page?

I would think that always bringing up a Squeak debugger is okay as long as  
the
Seaside page avoids having an inspector available ... that's the bit I  
don't like ...
In production web-page-based inspectors should never be allowed to come  
up ...
there's too much information that a clever person could glean from an  
inspector, not
to mention being able to evaluate arbitrary expressions.

If a Squeak debugger comes up, then the session would be blocked until the  
the http
connection timed out ... there are worse things that could happen.





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