* Cees Hek [EMAIL PROTECTED] [2005-11-28T20:47:16]
Also, I am guessing that you think this is a mailing list for generic
CGI related perl questions. In fact, this mailing list is
specifically for discussing the CGI::Application module which can make
life a lot easier for you when building CGI
* [EMAIL PROTECTED] [2005-12-19T22:21:25]
Influenced by a long thread that I started over the weekend about the
number of run modes allowed in an application, I've been breaking my one
large app into several. I have a question about turning control back to
another module.
We do this a lot,
* Mark Stosberg [EMAIL PROTECTED] [2005-12-20T17:20:18]
This works very nicely.
Interesting. This looks sort of like the sub_request that Catalyst has:
http://search.cpan.org/perldoc?Catalyst::Plugin::SubRequest
Why not use an external redirect, giving the resulting page a
* Michael Peters [EMAIL PROTECTED] [2006-06-05T12:29:51]
Rob Kinyon wrote:
Isn't a 500 more appropriate here given that 404 is more of a
webserver error and 500 is more of an application error? Yes, I
understand that C::A::Dispatch is playing a webserver on TV, but it's
still an
Did anyone (Mark?) look at the performance hit that Class::MOP will cause?
I've only taken a quick look, but it looks like the total user time to run test
suite goes up nearly 50% with this patch.
I'm assuming that a more hook-laden class will suffer even more. Benchmarks?
--
rjbs
* Rob Kinyon [EMAIL PROTECTED] [2006-07-02T23:00:18]
One thing I know that he and nothingmuch have been working on in Moose is
the ability to declare a class closed which will allow for Moose to cache
...yeah, I was wondering if that closed-ness feature was a MOP-ism or a
Moosism.
Of course,
* Jason A. Crome [EMAIL PROTECTED] [2006-07-12T21:13:24]
$self-cache-config({
driver = 'CacheFastMmap',
share_file = '/home/webapp/cache/mmapcache',
cache_size = '1m',
});
How about add_cache? You could alias add_caches and add a default_cache
method. Failing that, I'd suggest:
* Benjamin Reitzammer [EMAIL PROTECTED] [2006-07-13T05:02:28]
And just to add a little more opinion to this post:
I totally agree and think it's past time, to market Larger Thing Which
Has Not Yet Been Named a lot more.
I'd much rather get more work done on the Smaller Thing That CGI::App
* George Hartzell [EMAIL PROTECTED] [2007-09-06T19:43:33]
Have you looked at MIME::Lite or Net::SMTP, which make it pretty darn
easy to send a message? If they're not what you need, tell us why and
maybe someone can make a better suggestion.
Hi, I'm MIME::Lite's maintainer.
Please don't use
* George Hartzell [EMAIL PROTECTED] [2007-09-10T18:38:13]
[to the MIME::Lite maintainer]
Maybe some notes in the MIME::Lite docs about its shortcomings, or
requests for help fixing them, are in order?
I'll get around to it one of these days. In the meantime
* Jason Purdy [EMAIL PROTECTED] [2007-09-10T09:17:07]
We use MIME::Lite here a lot w/o any problems and certainly without
thinking it's horrendous. I will say that we don't do a whole lot of
email volume, but there's something about its API that resonates with my
style of coding, moreso
* Mark Fuller [EMAIL PROTECTED] [2007-09-12T22:54:33]
* George Hartzell [EMAIL PROTECTED] [2007-09-10T18:38:13]
Maybe some notes in the MIME::Lite docs about its shortcomings, or
requests for help fixing them, are in order?
I agree. I feel blindsided to learn I shouldn't be using
* Jason Purdy [EMAIL PROTECTED] [2007-09-12T23:44:36]
Perhaps you or someone should publish a similar series of columns
(unless they already exist) that does the same? As someone who is happy
with MIME::Lite, blissfully unaware of its problems and shortcomings and
jammed with work, I'm not
* Ron Savage [EMAIL PROTECTED] [2007-09-13T02:07:31]
o OK, so it's been superseded, but so what? That's no reason in an of
itself to change. As long as it works for you, keep using it.
[ ... ]
o But, since switching is comparatively easy, you might as well do it.
But my point is - switch
* [EMAIL PROTECTED] [2007-09-13T06:46:50]
Thank you for your e-mail message to BMG Parts Co.
The e-mail address you used ( [EMAIL PROTECTED] )is
not valid, so your message could not be delivered.
Somebody please remove this ass?
--
rjbs
* [EMAIL PROTECTED] [2007-09-13T06:49:49]
Buongiorno/Guten Tag
Sono assente fino al 17.9.2007. Ich bin bis am 17.9.2007 abwesend.
A presto!/Bis bald!
Chantal Gianoni
Can we remove this ass, too?
--
rjbs
-
Web Archive:
I want to do Stuff with OpenID. The way I see it, your OpenID right now can
only replace your password, not your username, in many applications. That's
because you want to be able to say:
http://some.web.app/user/USERNAME/whatever
Putting your OpenID, which is a URL, where USERNAME appears
I see that the devel version of CGI::Application uses Class::MOP. Neat.
Except...
On my 5.8.8 install, loading CGI::Application's stable release adds about 300k
to the resident size of my perl process. Loading metaclass.pm (of Class-MOP)
adds another 2000k.
In other words, moving from
* A. Pagaltzis [EMAIL PROTECTED] [2007-10-19T19:12:10]
* Ricardo SIGNES [EMAIL PROTECTED] [2007-10-19 19:45]:
Any other thoughts?
The default case is you use your OpenID to log into your main
account. So while you would need to create an account that an
OpenID gets associated with, you
* Michael Peters [EMAIL PROTECTED] [2007-10-19T19:28:20]
I've been wondering if the correct approach for handling this is to log in
using only your OpenID, and then let you choose a profile from among those
available. profile would replace the traditional user concept. Most
users would
I am not a big fan of HTML::Template. It just doesn't float my boat. It bugs
me a little bit that it's a prereq of CGI::Application, especially when it
isn't, then, really needed.
Is there a plan to convert HTML::Template from a prereq into a plugin?
Up-sides: no non-core prereqs as of 5.8,
I sent a number of posts to the list last night. Only one went through.
This morning, I tried the missing ones again. Nothing went through.
What's up?
--
rjbs
-
Web Archive:
Ages ago, I wrote a horrible wishlist tracker for my family. When my
grandmother was still the matriarch of the family, she was in charge of making
sure that everyone produced a wishlist. These were then circulated through
the mail, and everyone checked things off.
This was subsequently
I thought I'd drop the list a line (or two or three) with the stuff I want to
do soon, since it might be interesting, might inspire some people to help, and
might just help me get my thoughts together.
Rubric is an application I wrote some years ago, for storing tagged bookmarks
and notes. I
* Ricardo SIGNES [EMAIL PROTECTED] [2007-10-19T18:10:17]
I see that the devel version of CGI::Application uses Class::MOP. Neat.
Except it doesn't.
I thought, Hey, I'll just send Mark a patch to remove this. I had an ancient
checkout of CGI::Application, and I did a pull and saw:
Thu Aug
I didn't notice CA::Dispatch::Server when I was doing some poking at some code
the other day so instead I patched CGI::Application::Server to handle
::Dispatch modules.
I think this was a good mistake: CADS doesn't really strike me as being as good
a design as CAServer. In CADS, you say:
*
* Mark Fuller [EMAIL PROTECTED] [2008-03-10T09:06:30]
On Mon, Mar 10, 2008 at 3:56 AM, Ricardo SIGNES
[EMAIL PROTECTED] wrote:
stores your whole session in the cookie. It's stored as a base64-encoded,
Rijndael-enciphered, JSON-encoded string. This seemed like a swell idea
for me,
I
* Michael Peters [EMAIL PROTECTED] [2008-03-10T09:15:26]
Ricardo SIGNES wrote:
It's a Catalyst plugin that stores your whole session in the cookie. It's
stored as a base64-encoded, Rijndael-enciphered, JSON-encoded string.
Krang does this as well and I've used it on lots of other
* Mark Fuller [EMAIL PROTECTED] [2008-03-10T09:27:47]
On Mon, Mar 10, 2008 at 6:15 AM, Michael Peters [EMAIL PROTECTED] wrote:
I just use a URL encoded JSON cookie. I don't put anything sensitive in
there.
Is there a risk that this contributes to the bad reputation of
cookies? One
* Mark Fuller [EMAIL PROTECTED] [2008-03-11T10:52:29]
On Mon, Mar 10, 2008 at 9:54 AM, Ricardo SIGNES
I wouldn't use this for anything like banking or credit cards, but I feel
pretty okay about it for things like a Rubric login.
The problem (from my perspective) is that if it's encrypted
* Jaldhar H. Vyas [EMAIL PROTECTED] [2008-03-23T10:26:31]
I've been playing with Module::Starter recently and I wrote a plugin which
creates a basic CGI::Application based module. It should be wending its
way to CPAN as we speak.
Cool. Is there a reason it had to be a plugin and not just a
* Jaldhar H. Vyas [EMAIL PROTECTED] [2008-03-25T14:28:20]
Module::Starter is not as extensible as it could be.
So true! :(
I filed one bug about it already. I was going to wait till I could offer
some kind of patch before filing more. I would also like to see the ability
to add options to
* Mark Stosberg [EMAIL PROTECTED] [2008-06-21T10:53:56]
$t-param( c = $self ) if $var =~ /^c\./;
Is it correct that it should actually be this?
use Scalar::Util 'weaken';
$t-param( c = weaken($self) ) if $var =~ /^c\./;
No. Scalar::Util weakens the actual reference. It does not
* Mark Stosberg [EMAIL PROTECTED] [2008-06-23T16:05:54]
I agree. I have a pro account myself. It's a nice example of a Web 2.0
service in Perl.
I find it most useful for shared to-do lists, but use it for some
personal organization as well.
I really like it, and have blagged about that in
* Gmail [EMAIL PROTECTED] [2008-06-23T22:18:46]
In the OT vein, I'm curious what makes Hiveminder a Web 2.0 app, other than
the presence of a blog? Just curious.
It has some XMLHTTPRequest stuff, and a JSON API and probably some rounded
corners.
Does anybody know what Web 2.0 really means,
* Michael Peters [EMAIL PROTECTED] [2008-09-17T12:37:04]
Bradley C Bailey wrote:
In CAD::Server it tries to serve files staticly first before sending to
dispatch. I think the best solution would be to specify a way to mark an
entry point in the CA::Server config to specify static content.
* Mark Stosberg [EMAIL PROTECTED] [2008-09-17T20:57:37]
::Dispatch::Server prefers static files first, ::Server prefers dispatching
first
I think it is a bug in ::Server that it prefers dispatching server. The
recommended use of ::Dispatch, and also for Drupal, is to use a rewrite
rule
* Mark Stosberg [EMAIL PROTECTED] [2008-09-23T23:07:34]
I realized that I left some of the original code commented out in the
static-content.patch branch. I cleaned it up, tested it again,
updated the copy at http://shrimp.alerce.com/cgiapp, and have attached
the cleaner copy here for
* Mark Stosberg [EMAIL PROTECTED] [2008-11-01T22:15:50]
I'm willing to be a CO-MAINT for CGI::Application::Server, if that would help
move this along. I know you have dozens of other modules you maintain that
could keep you busy.
Sorry, the problem has actually been that *I* am comaint
I've released the new CGIApp server with the patches from George H. The main
tweak is that serve_response is now _serve_response to shut up pod-coverage
tests.
--
rjbs
# CGI::Application community mailing list
##
40 matches
Mail list logo