RE: [PEAR-DEV] pearifying metabase: preparing phase 2

> I don't think you need to worry about that now. I have a better > solution coming up in PHP 4.2: aggregate(). This is a new function that > lets you import methods from another class into an existing object. > This means we can simplify the architecture by having DB_connection and > DB_result objects importing backend-specific stuff on demand. This will > speed up simple calls a great deal (since there is less code to be > loaded always), and should reduce the result call overhead by > eleminating one layer of calls. Very interesting indeed ... Would such be the solution to our modularization problem? So that we can load functionality on demand? For example that the LOB stuff is only loaded when needed automatically by the db abstraction layer? I want to keep backwards compatibility to older php versions but this feature sounds really usefull. Anyways I have a lot of work ahead of me this week but I really want to have something by the end of the week that does proof that we are not completely nuts for attempting this merger :-) I will see how much I will be abl to finish, but I will focus on merging the structure not not so much on the details. Thx, for all the feedback. Best regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Alt Moabit 89 10559 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de _______________________________