[pLog-svn] Branch plog-1.1-ben - callgraph 1.1-ben

[Benjamin Krause]

Hey Allan,

Allan Sun wrote:

> As a developer outside the core team of Plog project, I gained a lot
> of beniffit from plog's nice MVC architecture, I've got a chance to
> look deep inside of the programme, I think the biggest weekness again
> is the architecture itself.

agree.. this architecture will work just fine in java, but it fails in
php. nevertheless i think we can (and will) use this framework in php :)

> To me I think we really need to review our architecture at this point,
> I did a simple check last night before I went to bed, I just realized
> that for a simple DefaultAction, there were 188 files been loaded, you
> know what? I just said WOWOOOO to myself, that really supprised me...
> Imagine what gonna happen when 100 guest browsing the web site at the
> same time? 18800+ files to be loaded! And the parsing and processing
> are not included!

this is what we're doing right now.. reducing the includes. and trying
to cache the most common queries not only within a session but for all
current visitors.

> I'm not sure how are we implementing the blog processiong ( I always
> use the plog framework but not the plog's blog funtion), but I
> thought, do I really need to have the email service when I read the
> somebody's blog? Shouldn't this service be included only when sombody
> post some comment or something like that? This happens to every where
> of plog.

fully ack :)

> So followed the discussion, I somehow agree with the idea of using
> class loader, but this will involve some more computing on finding the
> correct class, I believe it would be faster for small website, but
> again that's not for enterprise application.

i'm not sure about class loader either.. i think someone (oscar?) should
try to implement a generic class loader and we'll see how it works.. i
can currently not image a classloader that's flexible and fast :)

> My suggustion is really - refactoring! I do belive there are loads
> stuff we can do to improve the quality of the programme. I think what
> we need now is a good architecture but not any tricks on fast
> processing.

i think the architecture is good. sure some refactoring will help, but i
don't know how far you suggest to go with the refactoring..
just reorganizing the includes and implementing a cache might be
sufficient.
but i didn't yet analyse the speed if you manage to get a completly
uncached page (neither smarty cached, nor webapp-cached). and yes, i
fear the result is scary ;)

Ben