, google-able name would be nice. And naming writes go to the
man who does the work, so enjoy :)
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your
it sets for this. What is your PATH_INFO?
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http
of different things (like which
directories are on the filesystem, how apache is configured, etc).
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your
On 12/18/2011 08:14 PM, Ron Savage wrote:
Is anyone using Chrome's Javascript [1]?
Or heard of anyone using it?
It's used in some server-side javascript frameworks like node.js
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
}
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp
. It most likely would have happened no matter which
persistent environment you chose (FastCGI, mod_perl, Starman, etc).
Look for global variables or package variables. You should avoid those
for anything that changes per-request (or really changes at all).
--
Michael Peters
Plus Three, LP
# CGI
. Smolder's never been run on a
windows machine and I don't have one (nor the inclination really) to
help out with that. Patches would be welcome though as long as someone
else is willing to maintain them.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
::Application but it is not
listed
Yes, it's CGI::Application based.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options
, etc) environment will actually save you
memory on linux. Forked processes will do copy-on-write (COW) memory so
they will physically share the same memory even though logically they
have their own memory space.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
sizes this will probably
end up being an estimate rather than an exact cost. I'd probably
estimate on the high side too since no one likes to lose money on sales
and it does take time and effort to do the shipping.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing
On 11/26/2010 04:07 PM, Gurunandan R. Bhat wrote:
Is there something about using redirects under CA::Dispatch that I am
missing?
I use CA::Dispatch and redirects all the time. Although not from
CAP::Redirect. I instead use the header_type and header_props combo.
--
Michael Peters
Plus Three
- so some users are
obviously having trouble.
Anyone seen this before / got any ideas?
That seems like someone is pressing the stop button. That would kill the
connection and your server wouldn't notice until it tried to write to
that connection, thus the error.
--
Michael Peters
Plus Three, LP
that script (including your web app
package) and then starts executing the script. And you create and run
your application object before you run those callbacks, so you never see
them executing.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
under mod_perl can use
the same debugging toolbar as a CGI::Application app running under Starman.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your
after $webapp-run() has
already taken place.
But if you put the package into it's own file you wouldn't have this
problem since the runtime code in the package is run when the use
Private::Webapp statement is run.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp
new() on
every request and that is if you are doing something intensive at init
or setup time.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your
bottlenecks are.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp
not be exactly
what you're looking for, but it should give you at least a basis for
your own solution.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your
friend. Learn them and learn to love them.
2) If I hit an error in cgiapp_init, is there a way to redirect to an
error page, as per prerun_mode() ?
There doesn't appear to be. There's the error_mode() but that only seems
to work for run modes, not other stages.
--
Michael Peters
Plus Three, LP
Just a note that you can also use CGI::Application::Dispatch to
implement a REST interface as well.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change
2010] -e:
You've told Dispatch that your module name is
public::Packages::PublicSite when in fact it's just PublicSite.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
for example a situation where you have a single application
(same code) but you need to customize that application depending on
the URL that was accessed. Maybe it's a beta version, or a different
client, etc.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing
you only have a
single application module. I try to not have more than a dozen run modes
in any application file, and all but the simplest of applications will
have more than that.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
contantly hits to figure out if the
job is done. When it's done you can then redirect the client to where
you want them to go.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
Tregar's belly. But I'd be careful, he's got a mean
right hook :)
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options
have a patched HTML::Template that reads in the templates as UTF8, my
db connections are all UTF8 and I decode the CGI params as UTF8. As long
as all your inputs are UTF8 decoded then you don't need to explicitly
encode the output.
--
Michael Peters
Plus Three, LP
# CGI::Application
://mollom.com/) and Net:Mollom.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman
/ so that they aren't indexed like the things in lib/.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit
looking in there would also reveal more information as to why it failed.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options
be [cancel the test].
It doesn't really work like that. Apache::Test doesn't change your
apache config, it just uses the existing apache/mod_perl binary with
it's own config file.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
is done and it will probably timeout on you.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http
for Ajax.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp
knows
# how to deal with
print script type=text/javascriptupdate_progress(10)/script;
}
print /html;
return;
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
those.
Also, you're counting just raw lines which means you're counting
comments and whitespace (which penalizes modules which are well
commented). I'm not saying your criticism isn't valid, I'm just saying
that your data is too flawed to support that criticism :)
--
Michael Peters
Plus Three
it
(which means making the FH STDIN instead which might be trickier under mod_perl
or maybe not).
And then remember to close your workbook when it's done.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
Michael Peters wrote:
And then remember to close your workbook when it's done.
Also remember to send the right content type and other headers:
$self-header_add('-type' = 'application/vnd.ms-excel');
And if you're not going with CAP::Stream, then also mime-type, content-length
Apache. The big benefit though
is that they are Perl and can be installed from CPAN, which means that now
Smolder can be installed from CPAN.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
George Hartzell wrote:
When you use H::S::S + N::S::P, are you still using C::A::S on top of
them, or is there something else in the mix?
Not for Smolder, it just used C::A::S (which is a H::S::S subclass) and then we
have
sub net_server { 'Net::Server::PreFork' }
--
Michael Peters
Plus
to perform. I'd suggest you look into
having a dedicated job queue. You could use one of the existing frameworks like
Gearman or TheSchwartz, or you could write you own using something like POE or
Proc::Daemon+Parallel::ForkManager.
--
Michael Peters
Plus Three, LP
# CGI::Application
are fragile and as you correctly pointed out,
will suffer when scaled.
My queue also allows this, but I'm not sure how TheSchwartz or Gearman handle
that.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
setup {
my $self = shift;
$self-SUPER::setup();
# now do my own stuff
}
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message
Paul Miller wrote:
... but you're saying that what I'm doing will indeed work, it's just
better written with CAP::Stream?
You were using the correct idiom for dealing with large files. Don't read it all
in memory at once, but instead chunk it.
--
Michael Peters
Plus Three, LP
# CGI
;;
die Problem loading $pkg:\n\n$@ if $@;
},
no_chdir = 1
},
'/path/to/project/lib/MyProject'
);
}
caveat: not tested but should give you the general idea.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
a burden.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp
of a GET?
No, the request that follows an HTTP redirect are always GETs and you can't
force the browser to do something else.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
you send to the template easier.
Not to take too much away from this, but it doesn't test your template logic.
Now most of my templates are very simple, it's still logic and can therefore
have bugs.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
.
+ Archives don't need to be built into the system since other systems do
archiving and do it really well (http://www.markmail.org/)
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
Porta wrote:
+1 Mantle
+1
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net
Michael Peters wrote:
My biggest beef with Titanium is the name. It has these problems:
Another reason to not use it: It's already been taken.
http://snook.ca/archives/html_and_css/titanium
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
to something like mantul or mantl, but mantle is good too.
and not used much beyond geology.
Well, and fireplaces with a split spelling change :)
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp
this debate before and it's probably out of my hands, but I've
always liked taking a few swings with a stick at the deceased bodies of equine
animals.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
;
And then there is JSONP (http://en.wikipedia.org/wiki/JSON#JSONP) which is
basically returning Javascript that executes over some JSON. Really nice and
simple for mashups, etc.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
for flow control (I'm not
usually one of them) but some of them are very opinionated. Just wanted to bring
that up.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
silent wrote:
but it seems not work, all the request goto the default app default run_mode.
You don't show where you're using Mydispatch or how your using it.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
people start
using your app again in the morning after it's been sitting for hours without
any use. Under mod_perl Apache::DBI takes care of giving you a nice peristant DB
conection without you having to worry about things like timeouts.
--
Michael Peters
Plus Three, LP
# CGI::Application
features and bug fixes. For full details
please see the change log located at
https://sourceforge.net/project/shownotes.php?release_id=668591group_id=103045
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
Terrence Brannon wrote:
$app-forward( $app-start_mode ); # would be nice!
Are you saying that start_mode() doesn't return the start mode? It should.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
in that URL. If you only have 1
application module then you probably don't need Dispatch to begin with. And if you do add more later
then you're going to have problems since you'll need to change all those urls, so hopefully no one
has them bookmarked.
--
Michael Peters
Plus Three, LP
/journal/35037
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman/listinfo
module? I'd use Carp::cluck in your
run mode to get a backtrace of where exactly your method is being called from.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
() method. So in your init/prerun you'd do something like this:
$self-json_args(utf8 = 1);
And now that I think about it, all these json_* methods are kind of annoying. I probably should have
gone with $self-json-* instead. Oh well...
--
Michael Peters
Plus Three, LP
# CGI::Application
Stewart Heckenberg wrote:
I like MIME::Lite -- has a very simple attachment interface :)
MIME::Lite is what I've used in the past, although the Perl Email folks don't recommend it.
Apparently it's very crufty on the insides. I think they recommend Email::MIME instead.
--
Michael Peters
Plus
Justin Wyllie wrote:
How do I access CGI.pm methods like request_method() from my CGI::Application?
$self-query returns a CGI object. So just say $self-query-request_method.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
?
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp
the output of the AJAX response is. Some are very small HTML snippets,
but others are more complicated (lots of tables or forms, etc). So a template is very appropriate.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
$filefail ?
'fail' : 'ok')});
You need to use a CGI::Application::Plugin::* module within a CGI::Application based object.
Otherwise it can't add the appropriate methods or callbacks.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
really
diagnose the problem. My initial thought is that you're loading CAP::JSON before you set your base
class to be CGI::Application.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
plugin require me to be using a template?
No, not at all.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit
that works most/some of the time better than nothing?
If it were me, the answer would be no. A minor template change could break your application in
mysterious ways. I'd rather not have an HTML::FillInForm replacement than one that works sometimes
and not others.
--
Michael Peters
Plus Three, LP
about maybe using an XML module? XML::SAX has a pure perl driver. Maybe if your
HTML is XHTML it could work. Or if you want, you can probably use a libxml based module. It's
extremely common (installed on most systems) and has an forgiving/HTML mode.
--
Michael Peters
Plus Three, LP
# CGI
to Dispatch.
The webserver needs to make the decision as to whether or not Dispatch should
serve it, not Dispatch.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe
happy.
On a side note, get a hosting provider that gives you a compiler, gee wiz!
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery
() to be updated then look at
C::A::Plugin::Forward. If you need any cookies to be updated between run modes then you'll need to
go back to the client and then come back. Pretty easy and even easier with C::A::Plugin::Redirect.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing
fREW Schmidt wrote:
Ok, I have changed some things around in the hopes that it will fix my
issues, but I am still not having much luck...
If you're still having problems, post the debugging output from Dispatch.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
is never matched.
Dispatch dispatches based on the URL. In your case that URL is going to be index.cgi. Change the
action to be /save, keep your method as post and remove the name rm from that button (nameless
buttons are pretty common in web forms).
--
Michael Peters
Plus Three, LP
in. This
is the output I get (I added PATH_INFO) for the url:
http://locahost:8080/frew/controller_station/awesome
What is your document root? And what is your actual directory structure like
under that root?
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
/VirtualHost
#}}}
I think the Location probably tramples the DocumentRoot and
ScriptAlias directives.
Maybe not. What happens if you change them. Also, why are you using a DocumentRoot or ScriptAlias
directive when you're handling everything under '/' with that Location?
--
Michael Peters
Plus
point out that it works right on Ubuntu)?
You could try just putting in your own dispatch_path() method in your Dispatch class to strip out
the first directory part of the PATH_INFO.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
what I was planning on doing for the error log, and having all those urls,
etc in the error log would be a bit much since they aren't errors.
Thoughts?
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
about the security of their own machine and you won't be responsible if they lose their credentials.
Besides, if you were doing your passwords correctly, you wouldn't even be able to fill in the form
since you wouldn't know what it is, only they would.
--
Michael Peters
Plus Three, LP
# CGI
in the PATH_INFO. Try turning on
debugging and see if you can get any more information.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message
computers to remember their private information.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http
be happy to have it along. The easier it is for others to use the better. No need for them to go
hunting all over CPAN for it.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
figure out what module you're going to run and just call it's run()
directly after setting up a CGI.pm object with your thawed POST params.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
, but also the environment
you're running it in. If you run your tests just via the module but your application runs under
Apache, then there will be bugs that your tests don't catch.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
when handling them in
your application. You can get both from $self-query-param(). Something else is wrong with your
application.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
anyway.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp
Mark Stosberg wrote:
No big surprises, but perhaps interesting to take a look
Well, I think it goes to show all those people using CGI::Simple just to save .2M and .03s are
wasting their time :)
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
Michael Peters wrote:
No big surprises, but perhaps interesting to take a look
Another surprise for me is that Titanium has a startup time of .14s where C::A has .21s. Isn't
Titanium just C::A under the hood? How can it be faster?
Also you don't mention how many times you ran each
.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp
request then there's no reason to do it via require. In fact unless you're conditionally loading a
module there's no reason (unless you're doing something sufficiently magical) to use require it.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
. In this case it sounds like the OP controls his data source since he's having
problems sending it.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your
(which btw, does not have a friendly abbreviation :) do you plan on still using $c? Or will
you go with $t?
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe
became real variables in your program. This was fine unless you used one of those variables for
something else. This meant that anyone could craft a URL which would override a variable in your
program. Nasty things can happen.
--
Michael Peters
Plus Three, LP
# CGI::Application community
might reconsider this advice. Unless I'm missing something?
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit
your response as structured data (XML, JSON, etc)? If so, I'd just define a part
of the spec that lists your application specific error codes and what they mean. If your response is
not structured data, then just put a human readable error in the response.
--
Michael Peters
Plus Three, LP
can't give your tokens away to other
people.
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe, or change your message delivery options, ##
## visit: http
is more common than non-static (each
non-static page probably links to at least a dozen static files).
--
Michael Peters
Plus Three, LP
# CGI::Application community mailing list
####
## To unsubscribe
1 - 100 of 475 matches
Mail list logo
