[Seaside-dev] Issue 305 in seaside: move #nativeRequest to WARequestContext?

[codesite-noreply at google.com]

Comment #4 on issue 305 by jfitzell: move #nativeRequest to  
WARequestContext?
http://code.google.com/p/seaside/issues/detail?id=305

There may be people who need something from a native request and are  
willing to make
their application non-portable in order to get at it.

I assume Philippe means #remoteAddress is *now* part of WARequest, because  
it is. And
we should add other things to WARequest as they come up, of course, so that  
people
won't need the native request.

But I still don't really see what's wrong with providing access to the  
native one for
those who do want it. I just don't see why it should be stored on the  
Request instead
of the RequestContext at this point.

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