Mark Stosberg wrote:
We have a page on the wiki dedicated to this broad topic:
http://cgiapp.erlbaum.net/cgi-bin/cgi-app/index.cgi?BestPractices
If after reviewing that you are still curious, try framing a more
specific question about a particular aspect you are interested in
discussing the best
Mark Stosberg wrote:
On 2006-03-16, Paul Johnston <[EMAIL PROTECTED]> wrote:
Right - I have a plugin that is essentially very simple - we'll use the
blog example from previous thread.
I have created it with one Exported method (for example blog) which
stores the object in
Right - I have a plugin that is essentially very simple - we'll use the
blog example from previous thread.
I have created it with one Exported method (for example blog) which
stores the object in the calling objects private hash ie:
--- snip ---
package Plugins::Blog;
use vars qw($VERSION @EX
Just wondering if there is a "best practice" document, or suggestions on
best practice for creating a cgiapp application.
I have built several apps now, but all have been slightly different in
approach and ended up being quite different on completion.
Anyone care to share? I have looked thro
Cees Hek wrote:
All you need to do is export a 'blog' method from your
MyApp::Plugin::Blog plugin. This can be done quite easily using the
Exporter module. Here is a quick example of what you would put in
your plugin:
I'd got this far, but what I was confused about is what is returned?
ie
(this *may* be more a perl question as opposed to a cgiapp question so
apologies in advance if it is)
I want to create a module (like cgiapp::Plugin::DBH) that I can *use*
and then call directly from $self.
As an example, say that the application is a blogging application, and I
want to crea
Thanks for all your help regarding caching and queries and stuff.
I have experience of these kinds of things with many other languages,
just not really with perl, so you've given me a whole load of things to
look over and find out about.
Coming (back after 7 years) to perl from other language
Dan Horne wrote:
Optimising db connections: cutting down the number of DB connections per
request.
Paul, does your application need more than one connection per request? You
may be connecting to more than one database, schema or user, but if not,
then maybe you don't need so many connec
Michael et al,
Thanks for all the suggestions. The dbprof one is very useful, and
actually I've figured that the problem is 95% to do with the logging
I've setup in the system.
The bottleneck was in the fact I set up logging to debug the
applications easily, and it's writing to a file. Whe
Just out of interest, is there anything specific (pitfalls, known
issues) that I should be aware of when load testing applications built
on cgiapp?
I've just built what I think is a decent cgiapp (clean, small etc) and
have found that it's sluggish when under load. I've optimised the
database
I have installed it and am using it with the default login page and it's
working absolutely fine. However...
I want to be able to use it without the login page supplied so that I
can create my own that looks like the rest of the site (obviously). I
just can't seem to figure it out though.
Cees,
Thanks - makes a lot of sense and helps.
I'm currently using CGI::Session, and I'm glad I have. I prefer the
object interface.
Paul
Cees Hek wrote:
On 1/12/06, Paul Johnston <[EMAIL PROTECTED]> wrote:
Which is better?
How long is a piece of string?
Question:
Which is better?
Apache::Session
CGI::Session
is there a preference as to which one *should* be used?
It's not entirely clear to me why you would use one and not the other!
Paul
I am hung up on the Apache::SessionX dependency. I am trying to
install/configure it to use MySQL, but
(First post to this list, so hello!)
I haven't done perl for 7 years (long time) and am needing to come back
to it now for a web application and picked CGI::Application up. Great tool!
Just wondering if anyone has any Forum/Bulletin Board modules to plugin
to CGI::Application or recommendati
14 matches
Mail list logo
