[cep-dev] Request, Config, User

[Jackson M. <ja...@ph...>]

Marcus and I have been talking a little bit over IM the past couple of days 
trying to iron out some thoughts on the stuff in CEP that happens before a 
page module is loaded.  Here is the proposed idea:

There are three new objects that will be a part of every CEP request:

1) CEP_Config - replaces the (expensive) declaration of all those constants.

2) CEP_User - replaces the messy auth implementation and the nasty permissions 
array with a much more accessible OO interface.

3) CEP_Request - wraps up some information about the GET and POST variables.  
Controlling this allows us to  use clean and dirty URLs and do some fancy 
stuff with objects in forms (and entire forms as objects).  This object will 
most likely also contain cepCreateUrl() for creating new CEP requests (links, 
form actions, etc).

CEP_User is mostly working, and I have implemented it on my laptop, but I need 
someway to convert the requested string into a page module to load, so I am 
now working on the Config class.  Marcus is starting to think about the 
Request object.

CEP_User and CEP_Config will be cached in the session.  CEP_Request may be 
cached in the session.  Caching the request object would make it easy for us 
to keep a history of a particular user's requests (for going "back" after 
performing an action, etc).    But it will be a few days before we get there.

-Jackson