I believe there's a Java.pm module on CPAN that will allow a perl program
to instantiate java objects and call methods on them. That may or may not
be enough intercommunication for what you need.
Wes Sheldahl
Charlie Smith [EMAIL PROTECTED] on 06/09/2003 09:34:04 AM
To:[EMAIL PROTECTED]
Regarding the use of source filters, they only seemed to cause me trouble
under mod_perl. A while ago I tried using Switch.pm, another source filter
from Damian that provides a switch... case sort of syntax, together with
HTML::Mason and mod_perl. It led to some really strange errors that didn't
Hi,
I'm getting a bizarre compile error while trying to build
Apache::Scoreboard 0.10 on a Mandrake Linux 9.0 system.
Here's a snippet of make output, from the first gcc command that failed to just the
first few errors it generates:
gcc -c -I../
No, but you will need to recompile it plus lots of other modules, basically
any module that includes XS code. Consider using CPAN's autobundle feature.
:-)
Wes Sheldahl
Gazi, Nasser (London) [EMAIL PROTECTED] on 02/24/2003 06:24:32
AM
To:[EMAIL PROTECTED]
cc:
Subject:Upgrading to
No it hasn't. Need to use CGI::Cookie for the time being. Apache::Cookie
and Apache::Request I believe are both either provided by or dependent on
libapreq, which is still a work in progress for apache2/mod_perl2. That's
the biggest reason I'm still using Apache 1.3.x now.
Wes Sheldahl
Apache 1.3.6 is ancient, has numerous known bugs and security exploits.
Same for mod_perl 1.21.
Update to apache 1.3.27 and I think mod_perl 1.27, see if it still happens.
Wes
Hann, Brian [EMAIL PROTECTED] on 02/03/2003 11:43:23 AM
To:[EMAIL PROTECTED]
cc:
Subject:coredump with 3
I agree. There are probably more of us than might be immediately obvious,
too. If a mod_perl programmer doesn't see too many mod_perl jobs in their
area, they're likely to highlight other areas when they go job hunting even
if they'd rather do mod_perl and could do it well.
I wonder if
I use HTTP::WebTest for that sort of regression testing, just to make sure
nothing breaks along the way. I also use LWP and HTML::LinkExtor to check
some dynamically generated pages to make sure it's still generating valid
links. (It broke once, so after fixing I added a test for it... )
For
Any time you see an Internal Server Error, you should be looking in your
apache server's error_log file to see what exactly the error was. That will
help you (and the list) figure out what's going wrong.
Wes
Wei Gao [EMAIL PROTECTED] on 11/05/2002 06:10:34 PM
To:Perrin Harkins [EMAIL
Hi Jesse,
I really like your approach, and appreciate your explanation. I'm wondering
how you handle the packaging and installation; do you just use a shell
script to put the different pieces where they belong, or have you devised
something else?
Right now I'm also using CVS for my web
For the CPAN perl modules, check out the CPAN autobundle feature. It will
make a Bundle file of every perl module installed on your machine, which
you can then copy and install on the new machine. Installing the bundle
file will make it download and install all the CPAN modules. For the rest,
Check the mail archives for this list, there was a thread about using perl and
php together not that long ago. I think that one suggestion was to compile
mod_perl statically with apache, and to load php as a module. Also, you may want
to upgrade your perl to at least 5.6.1, if not 5.8.0. Are
Take a look at Exception::Class, which I believe uses Devel::StackTrace. Both
are available on CPAN.
I personally derived a lot of benefit from seeing how exceptions were done in
Alzabo (http://www.alzabo.org), even though I'm not using Alzabo itself in my
applications. All three modules are
When you View Source in your browser, are the img url's in the broken images
correct? Do you get any errors in your error log? anything strange in your
access log?
Wes
The Surprises [EMAIL PROTECTED] on 08/27/2002
01:37:14 PM
To: [EMAIL PROTECTED]
cc:(bcc: Wesley
The drawback could probably be at least partially mitigated with an inactivity
timeout. When they attempt to login, you check both the flag and the last time
you heard from them. If they had timed out, then you log them out and let them
go ahead and try to log in. It does cost an extra database
Does it help to update mod_perl to 1.27?
Wes
Pasquale Pagano [EMAIL PROTECTED] on 07/29/2002
12:35:10 PM
To: Modperl [EMAIL PROTECTED]
cc:(bcc: Wesley Sheldahl/Lex/Lexmark)
Subject: Problems using Perl v 5.8
Hi,
We have some problems using:
1) Perl v 5.8
2) Mod_Perl v 1.26
3)
Thanks, Iain! This helps explain some problems I ran into when I tried to use
Switch. ;-) Wish the Switch docs included some caveats about using it with
mod_perl
Wes Sheldahl
Iain Truskett [EMAIL PROTECTED] on 07/21/2002 11:10:25 PM
To: [EMAIL PROTECTED]
cc:(bcc: Wesley
That's true. However, you can deduct any expenses incurred in the course of
volunteer work, such as milage to and from the site, and so forth. Again, this
is in the US, YMMV elsewhere.
David Harris [EMAIL PROTECTED] on 06/20/2002 04:04:38 PM
To: 'Marc Spitzer' [EMAIL PROTECTED],
Just speaking as a mod_perl user/developer, I think the format of Rich's docs is
excellent. Since these are directives that belong in httpd.conf, it makes sense
for their documentation to look like the documentation of other non-perl
directives that belong in httpd.conf. Organization-wise,
Ow. That philosophy of 'make it impossible for the programmer to mess up' sounds
too reminiscent of Pascal and other straightjacket development environments. I
don't think there's any real substitute for well-disciplined, thinking
programmers. So my own quest right now is to develop more of the
By that do you mean DBI 1.24? That was just released a day or two ago IIRC.
Just checking,
Wes
Udlei Nattis [EMAIL PROTECTED] on 06/05/2002
03:39:00 PM
To: Stas Bekman [EMAIL PROTECTED]
cc: Perrin Harkins [EMAIL PROTECTED],
[EMAIL PROTECTED] (bcc: Wesley
One solution would be to put the javascript in its own .js file, and have every
page on your site reference that js file. Now every page will send a cookie with
the resolution information. You may want to adjust the server-side processing to
avoid duplicate database work, but that shouldn't be
This link offers some general guidelines for recovering from a compromised
server:
http://www.cert.org/tech_tips/win-UNIX-system_compromise.html
Hope it helps, and good luck.
Wes
Perrin Harkins [EMAIL PROTECTED] on 03/21/2002 03:42:55 PM
To: John Michael [EMAIL PROTECTED]
cc: [EMAIL
I can see how your approach adds functionality by performing as expected if
the user uses the Back button or opens the app. in more than one browser
window. The usual objection I've heard to using form fields is the security
risk of people changing hidden fields in ways unforseen before
You've addressed the issue of someone submitting a form with altered fields
to attack the server, and pointed out some more advantages, but I don't
think you've addressed the issue of protecting the hidden cleartext data
from others on the client side. I guess that's a matter of how paranoid you
Hi Alex,
The problem is that package FooBar doesn't have a new method. Here's what
happened as a result.
When you called 'FooBar-new($r), perl looked for a sub called new in package
FooBar. Since it didn't find one, it looked at FooBar's @ISA, and looked in
Apache::Request for a new method.
Use vim, namely the gvim or graphical vim editor, which works very well
under windows. syntax highlighting, full toolbar, and all the rest. If you've
tried vim before and the two modes gave you fits, there's now an Easy version
that doesn't make you switch between command and insert mode; can't
Hi,
I just started experimenting with Class::Singleton to store some static config
information. I subclassed it, put a couple test variables in it, and loaded in
my HTML::Mason page. Everything seemed fine. Then I added a simple warn
statement to the _instance_new() method so I could verify
1. Regarding the switch to postgresql, I think that's a good choice. Just pay
attention to postgresql's data types, and try to get your fields types and
lengths correct the first time if possible. It doesn't completely support the
ALTER TABLE command, so changing column types can be a pain,
... years ago ... Are you even sure he evaluated mod_perl and not Perl CGI
scripts?? Launching the interpreter and compiling every time might spike the
CPU. Like others have said, you would really have to benchmark the mod_perl and
Apache that you're using now; both have improved
Matthew Kennedy wrote:
Secondly, I've worked on a good-sized commerce site with
mod_perl+HTML::Mason. One of the more dirty secrets is that the back-end
of the site involves several standalone perl programs running as
daemons. What's even worse is; most of them have to sit in poll/wait
You might be able to do what you want without forking, and without tying up your
apache process while the database sync takes place.
Just write a server process using something like IO::Socket or POE (see
http://poe.perl.org). Have the mod_perl handler send a message to the separate
server
32 matches
Mail list logo
