Based on Karsten's submission of kristian's article, i'm leaning towards
phplib which i've worked with. it includes perm priviledges, db abstraction,
sessions mgmt, etc. etc. seems like maintenenance wouldn't be much if
the only thing in the phpWS code is the phplib class instances. But
i think this (or native sess, or ADODB sessions, etc.) might conflict
with the current way phpWS is architected for page output (eg. header->header,theme,footer->footer,
and module includes) which is obviously under scrutiny with all the theme
discussions.
Why rewrite classes that do the same thing... and do it well, IMHO.
PHPlib is quite easy to extend once its in place! BTW, if all this could
be replicated with native php4 sess, and phpWS functions without months
of lead time, i'd be all for it. Otherwise, i'm game to integrate.
__________________________________________________
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com
|
