At 09:14 AM 10/23/2001, Robert Koberg wrote:
For comparions, a nice aspect of j2ee applications IMHO is the
application server tends to be more general. ie. the application
server is not just the web server (as it is with mod_perl). I've found
j2ee features such as message beans, queues
However, I would have to say that I feel like coding
middleware in Java
is easier and more standardized, and well documented.
OK, so what are we missing? I feel like we're getting pretty close to
standardisation of middleware development with environments like POE (which
rocks, but is
Hi
I am new to mod-perl and am trying to migrate some
pretty large image scripts I have written to mod-perl.
I am attempting first to ge them to run correctly
under.
Apache::PerlRum
The scripts run, but sometimes through server
errors.
I am getting the following errors.
[Tue Oct 23 06:57:27
is easier and more standardized, and well documented. But I feel like
coding front-end web applications is much easier in Perl where the workflow
bits change all the time. For this, I like using SOAP on the backend Java
server and SOAP on the front-end Perl.
I don't quite understand the
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
I have a modperl site that accesses a number of modules.
In my startup.pl I have:
#!/usr/bin/perl -w
use strict;
use lib('/path/to/my/installation'); # 'site' directory is here
use Apache::DBI;
use Apache::StatINC;
use site::customers;
use site::orders;
use site::products;
use site::base;
1;
Chris Allen wrote:
If site::products calls functions from site::customers, do I need
a 'use site::customers' in site::products, when I have already
done a 'use' in my startup.pl?
No, but I always do. It's good documentation, to remind you that if you
ever ran this code outside of mod_perl
Matt Sergeant wrote:
OK, so what are we missing?
Based on the comments I've seen here over the years, and some on
Slashdot, the thing that seems to worry people the most is the lack of
an obvious message queue API in Perl. I've seen plenty of
implementations, but there isn't a plug-n-play
Perrin Harkins sent the following bits through the ether:
Perhaps a port of JMS is in order.
Interestingly, I've been thinking along the same lines. Spread
(http://www.spread.org/) can be used for the publish/subscribe
messaging domain but queueing seems to be important too. Straying a
bit
At 08:46 PM 10/23/2001, Rob Nagler wrote:
is easier and more standardized, and well documented. But I feel like
coding front-end web applications is much easier in Perl where the workflow
bits change all the time. For this, I like using SOAP on the backend Java
server and SOAP on the
At 09:45 PM 10/23/2001, Perrin Harkins wrote:
Matt Sergeant wrote:
OK, so what are we missing?
Based on the comments I've seen here over the years, and some on Slashdot,
the thing that seems to worry people the most is the lack of an obvious
message queue API in Perl. I've seen plenty of
Is anyone else using independent perl processes in a web app, or have strong
reasons not to?
Our web application (Metadot) provides a number of functions that are fulfilled by
a daemon written in perl. Among these are: collecting content from syndicated news
channels, sending email messages
At 10:36 PM 10/23/2001, Leon Brocard wrote:
Perrin Harkins sent the following bits through the ether:
Perhaps a port of JMS is in order.
Interestingly, I've been thinking along the same lines. Spread
(http://www.spread.org/) can be used for the publish/subscribe
messaging domain but queueing
-- [EMAIL PROTECTED] on 10/23/01 10:23:18 -0500
Is anyone else using independent perl processes in a web app, or have strong
reasons not to?
I use them for quite a few things. fork/exec works nicely in perl
(on unix at least), allows me to write daemons for most things.
Why do you ask?
Plows, Sean (London) wrote:
How can I set this as my cgi's can't locate my libs?
Regards,
Sean Plows
Sean - try use lib '/path/to/my/libs'; That should append your
library path to @INC.
Word on the street is that you NEVER EVER want to mess with @INC
directly.
Jon Robison
!Uniphied
On Mon, 2001-10-22 at 20:14, Robert Koberg wrote:
For comparions, a nice aspect of j2ee applications IMHO is the
application server tends to be more general. ie. the application
server is not just the web server (as it is with mod_perl). I've found
j2ee features such as message beans,
On Mon, 2001-10-22 at 21:27, Perrin Harkins wrote:
It sounds like the limitation there is that you're interfacing with systems
that can't notify you when something new happens. That's not Perl's fault.
If you wrote your daemons in Java alpahabet soup, they'd still have to poll
the pop3
Leon Brocard writes:
Perhaps a port of JMS is in order.
Interestingly, I've been thinking along the same lines. Spread
(http://www.spread.org/) can be used for the publish/subscribe
messaging domain but queueing seems to be important too. Straying a
bit offtopic perhaps, but I wonder what
At 11:27 PM 10/23/2001 +0800, Gunther Birznieks wrote:
At 09:45 PM 10/23/2001, Perrin Harkins wrote:
Matt Sergeant wrote:
OK, so what are we missing?
...
Based on the comments I've seen here over the years, and some on Slashdot,
the thing that seems to worry people the most is the lack of an
Is anyone else using independent perl processes in a web app, or have strong
reasons not to?
I use them for quite a few things. fork/exec works nicely in perl
(on unix at least), allows me to write daemons for most things.
Sure, our network is supported internally by a DNS daemon
On Tue, 2001-10-23 at 10:09, Gunther Birznieks wrote:
At 08:46 PM 10/23/2001, Rob Nagler wrote:
I don't quite understand the difference between worflow in the front-end and
workflow in the back-end. They both change. The danger of making one part
of the system easier to change is that
On Tue, 23 Oct 2001, Nathan Torkington wrote:
Of course, we couldn't call it a Java bean. They'd have to be Camel
droppings. :-)
Perl Jewels (Joules?)
-dave
/*==
www.urth.org
We await the New Sun
==*/
Stephen Adkins writes:
If no one suggests an appropriate list, I propose starting a p2ee group
on SourceForge. This gives us mailing lists and a CVS repository for the
artifacts of the effort (which will mostly be specifications and
documentation, with maybe some Bundle files). I would also
At 10:11 AM 10/23/01 -0600, Nathan Torkington wrote:
Leon Brocard writes:
Perhaps a port of JMS is in order.
Interestingly, I've been thinking along the same lines. Spread
(http://www.spread.org/) can be used for the publish/subscribe
messaging domain but queueing seems to be important
Matthew Kennedy wrote:
On Mon, 2001-10-22 at 21:27, Perrin Harkins wrote:
It sounds like the limitation there is that you're interfacing with systems
that can't notify you when something new happens. That's not Perl's fault.
If you wrote your daemons in Java alpahabet soup, they'd still have
On Tuesday 23 October 2001 18:21, Stephen Adkins wrote:
This issue of a P2EE specification has come up before
(and I participated in the discussion), but since it is off-topic for
the mod_perl list, I would appreciate some referrals of where to go to
discuss this.
If no one suggests an
Nathan Torkington [EMAIL PROTECTED] writes:
Leon Brocard writes:
Perhaps a port of JMS is in order.
Interestingly, I've been thinking along the same lines. Spread
(http://www.spread.org/) can be used for the publish/subscribe
messaging domain but queueing seems to be important too.
Nathan,
At 11:06 AM 10/23/2001 -0600, Nathan Torkington wrote:
Stephen Adkins writes:
If no one suggests an appropriate list, I propose starting a p2ee group
on SourceForge. This gives us mailing lists and a CVS repository for the
artifacts of the effort (which will mostly be specifications
Stephen Adkins writes:
That would be great (as long as perl.org can host the CVS too).
My concern was that perl.org might not be as specialized in hosting
development teams as sourceforge.net. Do you support viewcvs
or similar for web browsing of the CVS repository?
cvsweb. You can see
Stephen Adkins wrote:
If no one suggests an appropriate list, I propose starting a p2ee group
Can I just say that P2EE is a horrible, horrible name? It includes the
Java version number (when is J3EE coming out?), as well as Sun's
desperate attempt to make it sound like something you buy
PEP! (Perl Enterprise Project)! I like it!
Paul E Wilt
Principal Software Engineer
XanEdu, Inc. (division of Proquest Information and Learning)
http://www.xanedu.com mailto:[EMAIL PROTECTED]
300 North Zeeb Rd Phone:
Just out of curiosity: are there any
efficiency issues regarding using mod_perl for the exclusive use of a phase
other than the response? In other words, if I want a script to do
something other than return a static page from a file, are there
advantages/disadvantages to using mod_perl over
Gunther wrote:
If you do not have a strongly typed system, then when you break apart and
rebuild another part of the system, Perl may very well not complain when a
subtle bug comes up because of the fact that it is not strongly typed.
Whereas Java will complain quite often and usually early
At 02:28 PM 10/23/2001 -0400, Perrin Harkins wrote:
Stephen Adkins wrote:
If no one suggests an appropriate list, I propose starting a p2ee group
Can I just say that P2EE is a horrible, horrible name? It includes the
Java version number (when is J3EE coming out?), as well as Sun's
Hi there,
On Tue, 23 Oct 2001, John Michael wrote:
I am new to mod-perl and am trying to migrate some pretty large
image scripts I have written to mod-perl.
Have you come upon the Guide?
http://perl.apache.org/guide
It's a fairly weighty document by now but most of what you want will
be in
Hi there,
On Tue, 23 Oct 2001, Issac Goldstand wrote:
Just out of curiosity: are there any efficiency issues regarding
using mod_perl for the exclusive use of a phase other than the
response? In other words, if I want a script to do something other
than return a static page from a file,
At 3:38 PM -0400 10/23/01, Stephen Adkins wrote:
Several of you have made the same good point.
And now the naming flame war has already begun... ;-)
This is a discussion. Something has been proposed and it needs a
name. I'd hardly call this a flame war. A name is pretty important
and if
I have seen and read through the guide, but will read through it again as
you have suggested.
I do have use stricts in my scripts.
I also get a lot of these things when I run it with the -w option.
;' called at /usr/lib/perl5/site_perl/5.6.0/i386-linux/Apache/PerlRun.pm
line 113
Robert Landrum [EMAIL PROTECTED] wrote:
... A name is pretty important
and if it's acronym isn't easily recognized, it isn't going to gain
the support of developers. J2EE is catchy, so we need something
catchy. PEF isn't nearly as catchy as P2EE or P5EE or PEA (Perl
Enterprise API), but
I'm surprised that no one has, jokingly, suggested PEE.
Sorry, couldn't resist. :)
--
===
If you put three drops of poison into a 100 percent pure Java, you get - Windows. If
you put a few drops of Java into Windows, you
The list's goal is to create the Perl 5 Enterprise Extensions.
Send mail to [EMAIL PROTECTED] to join. When we've decided
on a path and start to code, I'll have a CVS repository created.
Nat
At 03:38 AM 10/24/2001, Stephen Adkins wrote:
At 02:28 PM 10/23/2001 -0400, Perrin Harkins wrote:
Stephen Adkins wrote:
If no one suggests an appropriate list, I propose starting a p2ee group
Can I just say that P2EE is a horrible, horrible name? It includes the
Java version number
I run into deep namespacetroubles I understand onyl vaguely and I cant workaround:
I have a script running under mod_perl that is called via two domains.
www1.domain.at/
www2.domain.at/sub/
both of the above addresses lead to the very same script (its the same
file on the disk, not a copy).
I had a routine in the beginning of the program to
initialze my variable hash and query param like so:
## initialize
globals ##foreach (keys
%VAR){$VAR{$_} = "";}
I did this so that these variables would not
propogate to other instances of the script.
This was
Folks, if this looks like an off topic, my apologies in advance...
I have written an accessing scheme that checks for the existence of
couple of cookies and if not present, the user is rerouted to a login
page. So far simple stuff. The problem is that my boss is saying that it
should work with a
Perrin Harkins wrote:
Chris Allen wrote:
[...]
Is $ENV{foo}='bar'; in startup.pl equivalent to PerlSetEnv foo bar
in httpd.conf?
Yes.
Are you sure? I experimented a few months ago, and found that
$ENV{foo}='bar'; would only last in each child until the first request
of the child
ged 01/10/23 13:09:56
Modified:.index.html index.html Added link to
email-etiquette.html
--
Log:
Revision ChangesPath
1.92 +2 -1
47 matches
Mail list logo
