[Solar-talk] Making a Solar::callback() method

[Pierre Oztel]

What I did back then was removing all View Helpers. I only kept the
getText() and getTextRaw() method, and made them available as Solar_View
methods.

This means no class_stack, no template_path_stack, no layouts. One view had
one possible template file, and each action had their own view : very simple
and fast. It was just a test, I am not using it.


I will now (in process) function refactor the callback in Sql package,
Filter and Valid classes and make an User cache system.

That may sound like crazy but I know exactly whats going on in the execution
scope, so I'll take advantage of that.

2007/8/3, Rodrigo Moraes <rodrigo.moraes at gmail.com>:
>
> On 8/3/07, Pierre Oztel wrote:
> >
> > Ah, I forgot to mention that I did some speed tests with the Solar_View
> > Object with and without the __call hook.
> >
> > In those tests, i removed View helpers completely. I had average times
> > of 100ms (without any opcode cache) with the hook, it falled down to a mean
> > of 20ms for this script on the bookmark application.
>
>
> Please clarify a bit: you tested the bookmarks app with Solar_View using
> call_user_func_array() versus using your callback() function?
>
> -- rodrigo
>
> _______________________________________________
> Solar-talk mailing list
> Solar-talk at lists.solarphp.com
> http://mailman-mail3.webfaction.com/listinfo/solar-talk
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman-mail3.webfaction.com/pipermail/solar-talk/attachments/20070803/a5aed6fc/attachment.html