How about this:
sub my_run_mode : DefaultRunmode {
# do something here
}
That looks entirely doable, and not even too difficult, but I am not
sure if I want to implement it,
mostly because the functionality is already in CGI::App, which defines
a default run-mode named start.
So you can
Cees,
it seems my assumption earlier today, that
sub start : Runmode {
}
would work as a default run mode, was partly mistaken.
It does work, but only if you override the setup in CGI::App,
because the default setup registers a start runmode as method
dump_html.
Since start is then
On 6/16/05, Thilo Planz [EMAIL PROTECTED] wrote:
How about this:
sub my_run_mode : DefaultRunmode {
# do something here
}
That looks entirely doable, and not even too difficult, but I am not
sure if I want to implement it,
mostly because the functionality is already in CGI::App,
Mark Stosberg wrote:
Rhesa wrote:
With the new proposed callback functionality, this could be added completely transparently. For the current version of cgi-app, it can still
be added with very little code. I don't think the utf8 code _has_ to be in there, but I needed it.
Do you think it
On 2005-06-16, Rhesa Rozendaal [EMAIL PROTECTED] wrote:
I've been playing with the new callback stuff, and it's quite neat! Well
done guys :)
Thanks.
I'm in the process of building a plugin for HTML::Tidy. The intention is
to convert the output into valid xhtml using tidy.
I'd like
I thought of the same idea as Cees independently and would also like to
see this happen.
Okay, I'll work on that.
Also, is there a particular reason to use StudlyCaps when this_style
is the convention for names in CGI::App?
If you refer to the Runmode attribute, all-lower-case attribute
Mark Stosberg wrote:
On 2005-06-16, Rhesa Rozendaal [EMAIL PROTECTED] wrote:
I'm in the process of building a plugin for HTML::Tidy. The intention is
to convert the output into valid xhtml using tidy.
I'd like something similiar, but different. I'd just like to see the
problems as warnings
I've had a number frustrations with CGI::Session and am considering
creating yet another alternative. What I have liked about CGI::Session
is the general interface. While I'm at home writing custom SQL, I liked
having the session code wrapped up in a neat little object, fairly
separate from the
From: Mark Stosberg [EMAIL PROTECTED] on Date: Fri, 17 Jun 2005 02:11:11
+ (UTC)
I've had a number frustrations with CGI::Session and am considering
creating yet another alternative. What I have liked about CGI::Session
is the general interface. While I'm at home writing custom SQL, I
I, for one, completely agree. I like the interface of CGI::Session, but
the implementation and level of support leave much to be desired.
I'd be happy to give whatever time and assistance I can to make this
happen. I started a thread or two on this at some point in the past,
but kind of let
Last month we talked about the possibility to have a pre-YAPC meeting in
New York when I am there.
So this is coming now. I'll be in New York between 18-22/June.
I'd be glad if a couple of us could get together for a beer or some
similar substance.
Local people, please set the place and the time
On Fri, 17 Jun 2005 02:11:11 + (UTC), Mark Stosberg wrote:
Hi Mark
Permit me to make a few comments.
I've had a number frustrations with CGI::Session and am considering
creating yet another alternative. What I have liked about
Apache::Session, although unsupported, may contain useful
From: Mark Stosberg [EMAIL PROTECTED] on Date: Fri, 17 Jun 2005 04:14:00
+ (UTC)
On 2005-06-17, David Emery [EMAIL PROTECTED] wrote:
On a related note, have you looked at Apache::Session? I've read
somewhere that it doesn't actually depend on mod_perl as the name
would imply.
I've
On Fri, 17 Jun 2005 13:54:27 +0900 (JST), David Emery wrote:
Hi David
The timestamp field bit seems pretty straight-forward, and I assume
most users want this for the sake of deleting old sessions.
CPAN is your friend.
CGI::Session::ExpireSessions
More info:
On 2005-06-17, Rhesa Rozendaal [EMAIL PROTECTED] wrote:
That would make a great addition during development, but I'm also using
it in production. It should be possible to make that configurable, so we
can accomodate both goals.
Final fixup is still a good idea though: you may be able to
Hi Mark
Just curious - would we be free to name the table and all the columns any way
we want?
I have my own policy on this:
http://savage.net.au/Ron/html/naming-database-objects.html
which, of course, I do not expect anyone else to follow...
--
Ron Savage
[EMAIL PROTECTED]
On Fri, 17 Jun 2005 14:51:29 +0900 (JST), David Emery wrote:
Hi Dave
I've heard that module was made in Australia and therefore unsafe
for civilized use. ;-)
Geomagnetically speaking, we're at the top of the planet, so for all the rest
of you I try to return SQL results upside-down, but you
17 matches
Mail list logo
