On 6/6/07, Tina Müller <[EMAIL PROTECTED]> wrote:
well, many people say, why optimize code if the database is slow anyway.
No offense, but those people are entirely correct. Choosing a
template module because of its speed when your application is
constrained by your database doesn't make sense
Sorry, but I suspect there's a mistake in your test. Possibly you
counted the time for JIT to do the initial compile, which is slow but
only happens once. HTML::Template::Compiled is fast, but it's not as
fast as JIT. I don't recommend actually using JIT though, since it's
harder to debug tem
On Jun 6, 2007, at 10:34 AM, Tina Müller wrote:
well, many people say, why optimize code if the database is slow
anyway.
i don't like that. if you can optimize by using a fast module - why
not?
and by the way, JIT doesn't have many features, while HT::Compiled has
the dot syntax.
Well wit
I ran some tests myself to compare the two about 6 months ago. It was a
"real world" test (an average sized template from my project), and I did not
count the compilation time for the JIT files. The difference between
HTML::Template::JIT and HTML::Template::Compiled was very small; smaller
th
hi,
On Wed, 6 Jun 2007, Octavian Rasnita wrote:
I don't use HTML::Template::Compiled though, because I found some bugs in
it.
well it was beta at that time, and it's actually still marked as beta on
cpan. you started to use the module really early.
now the biggest bugs have been fixed, and i
hi,
On Wed, 6 Jun 2007, Perrin Harkins wrote:
On 6/6/07, Octavian Rasnita <[EMAIL PROTECTED]> wrote:
> I have tested HTML::Template::JIT, but HTML::Template::Compiled was much
> faster than it.
Sorry, but I suspect there's a mistake in your test. Possibly you
counted the time for JIT to do th
Can someone point to a good place for docs on exactly how Apache starts.
I've had a read through ...
http://perl.apache.org/docs/2.0/user/handlers/server.html
.. and my Apache Modules book isn't answering the questions I have.
The problem is, I have startup.pl being run twice when
From: "Perrin Harkins" <[EMAIL PROTECTED]>
Sorry, but I suspect there's a mistake in your test. Possibly you
counted the time for JIT to do the initial compile, which is slow but
only happens once. HTML::Template::Compiled is fast, but it's not as
fast as JIT. I don't recommend actually using
On 6/6/07, Adam Tistler <[EMAIL PROTECTED]> wrote:
Even if you use AJAX, the page will still refresh because the AuthCookie
module's authentication method redirect's you back to the login page so that
the session cookie can be checked.
If it's your AJAX request getting redirected, that shouldn'
On 6/6/07, Octavian Rasnita <[EMAIL PROTECTED]> wrote:
I have tested HTML::Template::JIT, but HTML::Template::Compiled was much
faster than it.
Sorry, but I suspect there's a mistake in your test. Possibly you
counted the time for JIT to do the initial compile, which is slow but
only happens o
Try "PerlInterpScope request" and see if the coredumps disappear. Further
check if it's always this place.
PerlInterpScope request did not help. I just tested, and still got a
segfault.
As far as I have seen, all the segfaults seem to be mgv related, but not
at the exact same spot.
One odd
On Wednesday 06 June 2007 10:55, Jani M. wrote:
> (gdb) btt 4
> [Switching to thread 4 (process 2133)]#0 0xb77eb15a in
> modperl_mgv_as_string (my_perl=0x8662c58, symbol=0x8178190, p=0x8938438,
> package=0) at modperl_mgv.c:399
> 399 modperl_mgv.c: No such file or directory.
> in
Perrin Harkins wrote:
> Honestly, the person who has done the most work on debugging thread
> crashes is Torsten. His advice on how to debug it will be better than
> mine. It does seem like people usually solve them by using backtrace
> analysis though.
Getting back to this, I've now had time t
Even if you use AJAX, the page will still refresh because the AuthCookie
module's authentication method redirect's you back to the login page so that
the session cookie can be checked. You might be able to get around that by
overloading the authentication method using a subrequest instead of a
re
14 matches
Mail list logo