[Phrame-devel] Idea(s)(ls) regarding Phrame's internals

[Pieter v. S. <pvs...@ya...>]

All,

I follow the disussion on Phrame lite and heavy
versions in this list with much interest. Arnold's
intention to utilize a modular design 'sounds like
music in my ear' as the Dutch saying goes. I hope
though that Phrame's internals will remain as clean
(i.e. avoiding unnecessary complexitity) and 'PHP
minded' as possible. 

With this in mind I was looking at Alex Belgraver's
additions to Phrame. Some of his classes definitely
add more Struts flavour to Phrame and improvements
like the dispatching / forwarding mechanism are in my
opinion indispensible to push Phrame towards 'industry
strength'.

As an example of the above, I wondered if some of the
'complexity' in HttpSession and HttpRequestServlet
could be reduced: 

(1) Why isn't HttpSession just be a wrapper around
$_SESSION? This would also provide compatibility with 
components utilizing $_SESSION directly.

(2) Why isn't HttpServletRequest->_requestState just a

wrapper around $_REQUEST? As far as I can see, putting
values in _requestState will not be reflected in
$_REQUEST, which could cause problems for components
utilizing $_REQUEST directly.

(Alex, please regard this comment as positive
criticism; I'm very impressed by your additions.)

Best regards,
Pieter van Stempvoort

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com