Terrence Brannon writes:
really? it looked like display logic to me... I downloaded the
distribution.
Please let us ([EMAIL PROTECTED]) know what you think.
the thing that I found unsavoury about this framework was that
all the classes were
Bivio::* instead of something general and
[EMAIL PROTECTED] writes:
to the big iron in back. To a corporation, such as the one that employs
myself, if you don't have big iron you don't understand what 'Enterprise'
means.
I used to work at Tandem doing CORBA ORBs in Java and C. Yes, you
need middleware for this type of stuff. The
Matt Sergeant writes:
Compared to hacking perl code - absolutely Plus SP's are almost always
harder to debug
don't forget about versioning and backing out changes It's one thing
to deploy an RPM and revert it to the previous version It's another
to back out a stored procedure change
Stephen Adkins writes:
There are going to be an increasing number of cases where
the P5EE needs a core server, separate from the web server.
(Similar in some respects to how an EJB server is separate
from the web server in which Servlets run.)
I think the reliability/flexibility/security of
Sorry, this isn't what you want to hear...
If you want to gain acceptance in the enterprise, solve a problem
for them. CORBA, with all its backing, failed to succeed as well as
Java and .NET. It takes people with vested interests and power/money
to make things happen.
Let me give you a
Stephen Adkins writes:
I will be downloading bOP and evaluating making P5EE work
with it.
I don't think many people are interested in a bOP adapter.
Rob: Does this seem like a good idea, and would you and
bivio Software Artisans, Inc. look kindly on such a
development?
We always like
Stephen Adkins writes:
I don't think many people are interested in a bOP adapter.
Do you mean people on this list? Why would that be?
or people you have talked to over the last year?
No one uses bOP except us, and bOP is all we need. If we needed more,
we'd add it. You might want to look
Stephen Adkins writes:
As always, all feedback is welcomed.
Firstly, I think you're doing a great job trying to lead this effort.
It takes a tremendous amount of willpower to deal with curmudgeons
like be. :-)
Secondly, now that I think I understand your motives better, I wonder
if there is a
Leon Brocard writes:
P5EEx::Blue has nothing to do with enterprise. I don't know of anyone
using the code at all, let alone scaling it up, so we'd be giving the
wrong impression by labelling it as P5EE.
Well, depends on what you mean by enterpise. When J2EE was first
released, it wasn't used
James Duncan writes:
Yes, it is a boogie man. As yet I've not seen any general consensus on
what p5ee actually should do; it seems a little premature for voting on
a code-base for the *enterprise* edition of Perl.
What about Java's write once, run anywhere. It still isn't true.
Marketing is
James Duncan writes:
But who is going to market P5EE?
No one, but it still has to have a name. P5EEx::Blue is just too hard
to pronounce.
is all valid stuff -- I don't think however, that it can become the
signed, sealed and certified P5EE.
Who has the authority to sign, seal and deliver
Adam Turoff writes:
From that page, I don't see any concrete details on what features
are found in an enterprise system, which of those features are
lacking in Perl today (if any), and why this lack of features needs
to be addressed with P5EE.
In J2EE, they have tried hard to provide:
Tatsuhiko Miyagawa writes:
There's also another logging module Log::Dispatch::Config by me.
And, from bOP:
http://petshop.bivio.biz/src?s=Bivio::IO::Alert
http://petshop.bivio.biz/src?s=Bivio::IO::Trace
:)
Rob
One problem I didn't see addressed: partial context clearing before
internal redirects. We didn't consider this problem in our first cut,
but later added put_durable to our Request (context) object. Once
we get around to it, we will be clearing non-durable state when an
internal redirect
Stephen Adkins writes:
QUICK AND DIRTY SINGLE-SERVER SOLUTION
I implemented a quick-and-dirty single-server solution, where
I use a single server to process requests. I simply poll the
request table in the database once a minute for new requests,
and if they exist, I process them.
Now I
Stephen Adkins writes:
The server(s) connect to a mainframe and perform time-consuming,
repetitive transactions to collect the data that has been requested.
Thus, these servers are slow, waiting several seconds for each
response, but they do not put a large load on the local processor.
So I
Stephen Adkins writes:
However, I have been thinking about asynchronous execution, queues,
and queue-working, and I wanted to get a handle on how best I should
solve the problem in a general way.
I guess this is where we diverge. It sounds like you have a
specific problem. Generalizing at
Perrin Harkins writes:
I try to code it so that the business logic is not dependent on a
certain runtime environment, and then write a small mod_perl handler to
call it.
I've been doing a lot of test-first coding. It makes it so that you
start Apache, and the software just runs. With
Gunther Birznieks writes:
In the context of what you are saying, it seems as if everyone should
just stick to using TCP/IP/Telnet as a protocol and then the world would
be a better place.
Once upon a time, there was OSI, SNA, DECnet, etc. Nowadays, all
computers talk IP, even if you
Gunther Birznieks writes:
If you had an Apache server and a POE app server, what would a cracker
have an easier time trying to get in?
Assuming up-to-date code, POE, for sure.
Probably the Apache server. Once broken through the Apache server, the
cracker would have to figure out that it is
Gunther Birznieks writes:
That will surely be easier than figuring our the vulnerabilities for
myself. Allowing an exploit to be posted will let me be a part-time
cracker and all I need to do is wait with a skeleton of injection code,
ready to strike when the exploit is publicized. But in
Matt Sergeant writes:
There's a huge difference in what they are trying to achieve though.
POE doesn't open any files and it doesn't write any files to disk. None
of it is written in C (yet), so unless there's a buffer overrun or type
mismatch bug in perl you can exploit, you're not going
Gunther Birznieks writes:
I am not sure it is a bad example. It is an extreme example, so
therefore biased, but Apache is also a biased project because of
Apache's role in the Web.
Agreed.
That's true. But if you have a collocation facility, you also don't have
an intranet on the other
Bas A.Schulte writes:
still is something I haven't figured out. Basically, I need some way to
coordinate the children so each child can find out what the other
children are doing.
Use a table in your database. The DB needs to support row level
locking (we use Oracle). Here's an example:
Rocco Caputo writes:
Rating all of CPAN according to the quality of the average module does
a disservice to its better half. Depreciating its good distributions
also feeds into the myth that all Perl software is shoddy.
That isn't what I said. I program Perl daily. I use a bunch of CPAN
on
Perrin Harkins writes:
I think you are vastly over-estimating how much effort JMS/EJB/etc.
would save you.
EJB doesn't save you anything. It creates work and complexity,
esp. Entity Beans. I've built large systems using EJB and Perl. The
Perl project was built faster, with fewer people,
Perrin Harkins writes:
Bas A.Schulte wrote:
I do when the delivery mechanism has failed for 6 hours and I have 12000
messages in the queue *and* make sure current messages get sent in time?
I don't know, that's an application-specific choice. Of course JMS
doesn't know either.
This is
Rocco Caputo writes:
I think it's not fair. Despite POE's widespread adoption by hobbyists
and enterprises alike, I'm still not convinced it's ready for the
Enterprise label. To be sure, I'd love to call POE P5EE Enterprise
Certified or something, but not before its time.
Unless there is a
Dave Rolsky writes:
I've never written an app for a client that started on one backend and
moved to another. I imagine that if this were to happen, it'd be because
the new backend provided some set of features that were now important to
the app, and some code changes would be necessary to
29 matches
Mail list logo
