On Sep 8, 2005, at 00:30, [EMAIL PROTECTED] wrote:
This patch fixes tests for "legacy" versions of perl.
Tested against :
5.004_05
5.6.0
5.6.1
5.8.0
5.8.5
Tested against 5.8.6 here, and applied. Thanks again.
--
Rocco Caputo - http://poe.perl.org/
On Sep 7, 2005, at 23:04, [EMAIL PROTECTED] wrote:
This is a patch to POE that detects faulty IO:Polls. (That is,
ones that
don't have POLLRDNORM and other important constants defined.) It also
causes a test case to be SKIPed if the Kernel can't be loaded.
Applied, thank you.
code if you using Acceptor.
It is documented and includes a test cases.
Thanks! I applied this with a version of the test cases that doesn't
use fork(). You said that fork() was necessary to avoid badness in
Linux, so I'm not going to upload this to PAUSE right away.
--
Rocco Cap
Casey West's POE::Session::MultiDispatch may do what you want. See:
http://search.cpan.org/~cwest/POE-Session-MultiDispatch/MultiDispatch.pm
--
Rocco Caputo - http://poe.perl.org/
f you have the time, please send back a version that fails
on your system. I can use it to hunt down the problem, assuming I
can find a system where it fails for me.
Thank you.
--
Rocco Caputo - http://poe.perl.org/
hicks-wheel-run-no-stdin.perl
Description: Binary data
program is trivial. Is there a sufficiently nontrivial test
program that illustrates Perl's signal handling is less than robust,
even in the 5.8 series?
--
Rocco Caputo - [EMAIL PROTECTED]
poe-time-adjustments.perl
Description: Binary data
On Sep 5, 2005, at 21:37, Jay Strauss wrote:
Rocco Caputo wrote:
On Sep 5, 2005, at 17:43, Jay Strauss wrote:
I'm getting "POE::Kernel's run() method was never called." error
when my script that calls the code below ends.
I could put a ->run and ->("shut
nt::HTTP
at its current revision, I would be happy to apply it.
--
Rocco Caputo - http://poe.perl.org/
\0//) {
$read_length = $1;
next;
}
my $octets_read = sysread($socket, $buffer, 4096, length($buffer));
return unless $octets_read;
}
}
--
Rocco Caputo - [EMAIL PROTECTED]
n and ACE for C++.
--
Rocco Caputo - [EMAIL PROTECTED]
ou daemonize the program before starting any sessions?
Any pointers how to continue debugging/solving this issue?
Determine what Proc::Daemon::Init is doing.
How would that force child processes to close their sockets, or
simulate the behavior from the parent process' point of view?
--
Rocco Caputo - [EMAIL PROTECTED]
On Aug 27, 2005, at 17:46, Jeff Lowrey wrote:
On Sat, Aug 27, 2005 at 05:16:06PM -0400, Rocco Caputo wrote:
On Aug 26, 2005, at 16:27, Jeff Lowrey wrote:
use POE::Component::Server::MDP::POEQueueProvider;
Wow, that's long, and Provider seems to overlap with Server.
POE::Component
nce I've poked at the
project. If you have some time and inspiration, grab yourself a copy
from the repository: svn co https://thirdlobe.com/svn/poe-stage/trunk .
--
Rocco Caputo - [EMAIL PROTECTED]
from the filter's parsing buffer, returning zero or more complete
data structures. This performs the task commonly known as
deserializing, thawing, or cooking.
Your filter is done once you have written those four methods. The
real work comes after that: Documenting, writing tests, and releasing
your code on the CPAN.
--
Rocco Caputo - [EMAIL PROTECTED]
will be a lot of
modules below POE::Component::MDP.
Any objections to the namespace? Better suggestions?
"Perl Messaging Service" has already been rejected... ;-)
Perl Queuing Runtime Server Thingy? :)
--
Rocco Caputo - [EMAIL PROTECTED]
efore handing @_ to the ClientConnected callback. It works
well, too. I'll release POE 0.3201 after I'm sure I haven't broken
anything along the way.
Thank you again for the test case and a very detailed account of the
problem.
--
Rocco Caputo - http://poe.perl.org/
manager, and the only solution is to
upgrade your operating system, then I suppose the release will just have
to wait.
--
Rocco Caputo - http://poe.perl.org/
he people in charge of your favorite package manager.
I will not roll back the supported version of File::Spec without a
really good reason. POE development already suffers from a commitment
to supporting multiple versions of Perl. Multiplying that by multiple
module versions is out of the question.
--
Rocco Caputo - http://poe.perl.org/
rough comments, bug reports or patches. POE
wouldn't be nearly as cool without you.
--
Rocco Caputo - [EMAIL PROTECTED] - http://poe.perl.org/
BI->connect() in
subprocesses. Since DBD::Oracle's clobbering a child process' SIGINT
handler, your main program should remain unaffected.
--
Rocco Caputo - http://poe.perl.org/
ons from many different
> clients.
POE::Component::Server::TCP handles multiple concurrent connections.
--
Rocco Caputo - http://poe.perl.org/
quester can cancel a request it has made by allowing it
to destruct. delete($self->{req}{foo}) cancels $self->{req}{foo}.
Finally, the convention of storing new requests within the current
request causes request destruction to be chained. Canceling a
top-level request will also cancel the tree of sub-requests beneath
it.
Thanks for reading.
--
Rocco Caputo - http://poe.perl.org/
;d appreciate
it if you could try the development version before it's released.
It's available from https://thirdlobe.com/svn/poco-client-http/trunk/
--
Rocco Caputo - http://poe.perl.org/
tp://rt.cpan.org/NoAuth/Bug.html?id=13127
http://rt.cpan.org/NoAuth/Bug.html?id=11553
You'll be less happy to know that the fixed version hasn't been
released to CPAN yet.
Thanks for the test results and perl -V output. They confirm that the
problem you're having matches the one that was previously reported.
--
Rocco Caputo - http://poe.perl.org/
; it nor one for _default
>
> what does it mean?
It means that one of your sessions received a _child event (documented
in POE::Session) but does not have a handler for that event. This is
a "lost" event. It would normally be discarded, but
POE_ASSERT_DEFAULT turns it int
set POE_ASSERT_DEFAULT=1 in your shell. This will enable POE to
check the sanity of things you're doing. By default the checks are
off to avoid a corresponding performance penalty.
--
Rocco Caputo - http://poe.perl.org/
l a new one from that list as old ones are
finished.
2. Use delay_add() rather than yield() or post() to put the events in
the queue with a small random delay. This doesn't produce optimal
friendliness, but it does allow URLs from multiple sites to mix.
$kernel->delay_add( fetch_url => rand(), $url );
--
Rocco Caputo - http://poe.perl.org/
n you cobble together a short test case?
--
Rocco Caputo - http://poe.perl.org/
t_state, $start_event );
That spawns a new POE::NFA instance, enters its initial state, and
fires off an event that notifies the session that the state has been
entered.
The next clue in this puzzle is goto_state() itself. Its third and
subsequent parameters are passed as arguments to the $start_event in
the state being entered.
I hope that helps.
--
Rocco Caputo - http://poe.perl.org/
OFs
isn't rocket science if last year's any indication. Stake a claim on
a room and a time slot, and you've organized a BOF. The hardest part
is letting people know it exists.
--
Rocco Caputo - http://poe.perl.org/
ient::SMTP namespace on CPAN.
No objections from me. As far as I know, you're the first person to
plant a flag in that namespace.
--
Rocco Caputo - http://poe.perl.org/
do",
>SuccessEvent => "insert",
>FailureEvent => "failed",
>HandleId => $dbh_id,
>Args => [ $sql],
>);
It looks like the author of LaDBI doesn't read the list. Maybe you
can contact him directly? His e-mail address is in the documentation.
--
Rocco Caputo - http://poe.perl.org/
uot; when
nobody has events registered for them. This should fix both problems.
--
Rocco Caputo - http://poe.perl.org/
quot;next interesting"
> datetime.
>
> When the "next interesting" time has come, I start the specified task
> (in my case, I open a tcp/ip network connection to a local control
> server, also a POE app, and tell it to do something.
>
> It beats the hell out of regular cron, flexibility-wise ;)
Sounds nice! Have you seen POE::Component::Cron?
--
Rocco Caputo - http://poe.perl.org/
How about:
If there's nonzero-length content
And there isn't a Content-Length header
We go ahead and add one?
Would that cause damage anywhere?
If so, is there an alternate solution that would cause less (ideally
no) damage?
--
Rocco Caputo - http://poe.perl.org/
OE::Filter::Stream
-- Examples of protocol abstractions.
POE::Loop::*
-- Event loop abstractions and bridges to external event loops.
Also see CPAN for other examples.
It would also be fair to inform you that these are just different ways
to do similar things. Since POE is layered and Perl-based, you're
certainly free to write new abstractions that are more specific (and
finer-tuned) to your application. We also like patches. :)
--
Rocco Caputo - http://poe.perl.org/
components, I'm guessing that you've reached a shell or
system limit on the amount of resources you're allowed to consume.
Talk to your system administrator about your system's resource limits.
--
Rocco Caputo - http://poe.perl.org/
nd
application can stand before performance is too poor to continue.
Sessions don't use a constant amount of resources (CPU cycles, file
descriptors, bytes of memory, etc.).
--
Rocco Caputo - http://poe.perl.org/
On Tue, May 03, 2005 at 11:47:19AM +0400, Alex wrote:
> How to make as much childs as possible, but not more than
> (for example 50%) of CPU.
I don't know. How does one portably determine their machine's idle
CPU percent?
--
Rocco Caputo - http://poe.perl.org/
array into hash"
$_[HEAP] shouldn't be an array reference unless you've done something
sneaky. Maybe you're saying:
my ($heap, @stuff) = @_;
It should be:
my ($heap, @stuff) = @_[HEAP, ARG0, ARG1, etc.];
Or you've otherwise mismatched the variables with their elements in @_ ?
--
Rocco Caputo - http://poe.perl.org/
On Fri, Apr 29, 2005 at 01:49:59AM +0800, Jonathan Gill wrote:
> Im trying to use a POE::Component::TCP::Client to send a single line to
> a server (on a remote machine)
>
> I send the message with a
> $heap{server}->put($mymessage);
Shouldn't that be $heap->{serv
buffer to the Wheel::ReadWrite after
a connection is made.
2. Use a "put" message, and do the buffering internal to Client::TCP:
$kernel->yield(put => "text");
This will add new latency to outgoing messages, and it will conflict
with $heap->{wheel}->put() in the same ways that mixing buffered and
unbuffered I/O do.
--
Rocco Caputo - http://poe.perl.org/
On Tue, Apr 19, 2005 at 12:28:20PM -0400, sungo wrote:
>
> Rocco Caputo wrote:
> > POE 0.31 has been on the PAUSE for a day or two.
>
> which of the scheduled deprecations actually took place in 0.31?
None of the scheduled deprecations happened between 0.3009 and 0.31.
Search
summary here, but you're welcome to read
the full list at http://poe.perl.org/?POE_CHANGES .
Thank you for your help. A lot of POE's development comes from people
on this list, whether through comments, bug reports or patches. POE
wouldn't be nearly as cool without you.
--
and other
vandals can't edit them.
If you check out POE's "extras" module, the wiki source and templates
are there. One of the committers can apply your patches to them.
That would be
cvs co extras
from wherever you've checked out POE itself.
--
Rocco Caputo - http://poe.perl.org/
On Tue, Apr 12, 2005 at 03:54:57PM +0200, Merijn Broeren wrote:
> Quoting Rocco Caputo ([EMAIL PROTECTED]):
> >
> > Failed Test Stat Wstat Total Fail Failed List
ince the test program explicitly calls C
at its end. I've verified that it gets that far, too.
I've committed the changes anyway. You can check them out and check
out the results yourself. The error will need to be cleared up
somehow before I release it to the CPAN.
Thanks again.
--
Rocco Caputo - http://poe.perl.org/
ink a better idea is to have whoisHandler return RC_WAIT (see
perldoc POE::Component::Client::HTTP) and pass $nick and $response to
the IRC part.
The IRC part can send its whois request to IRC, build the content for
$response, then call $response->continue() to pass the response back
to the browser.
To be sure, you could have the IRC bot deposit data for Apache or some
other web server to pick up. The responses won't be realtime, but
that may not be an issue.
--
Rocco Caputo - http://poe.perl.org/
ent::Server::XXX classes.
How about the "shutdown" command for POE::Component::Server::TCP?
Posting that to the component alias (rather than an individual
connection) will stop the server but should allow existing connections
to finish.
--
Rocco Caputo - http://poe.perl.org/
27;s a good interface by poe standards
I've proposed another OSCON tutorial for this year covering parts of
#3 and #4. If it's accepted, I'll be beating my head on a new
presentation for the next few months. Wish me luck!
Historically POE hasn't defined best practices for component
interfaces, but David Davis is leading the group to change all that.
Hopefully he'll chime in with a status report. :)
--
Rocco Caputo - http://poe.perl.org/
d checks.
There may be a good reason for it, but I've usually kept away from
Filter::HTTPD and don't know it. It may be squeamishness towards
supporting file uploads (which would be buffered in memory), but
that's just a wild guess.
--
Rocco Caputo - http://poe.perl.org/
ls get
> handlers. That might explain why I can't Ctrl-C when I include POE, but
> it doesn't explain why I Ctrl-C segfaults when I include both POE and
> DBD::Sybase.
I don't want to sound cold-hearted, but you should probably try the
test case against the latest CPAN release of POE. The newer signal
semantics may solve your problem.
I'm sure hoping they do, anyway. :)
--
Rocco Caputo - http://poe.perl.org/
But the example in the gray box below that shows it being called with
> only one argument. Is that single-argument call actually legal? If
> so, maybe the docs should be tweaked? :-)
The documentation was wrong, but now it's fixed. Thanks for spotting
the error. :)
--
Rocco Caputo - http://poe.perl.org/
e() when called
by POE::Kernel itself. Maybe adding
die unless $poe_kernel;
die if $poe_kernel->get_active_session() == $poe_kernel;
would solve that.
--
Rocco Caputo - http://poe.perl.org/
ple could evaluate it, comment upon it, and come up with a generic
mechanism for POE exceptions. We're still waiting for that general
pattern to emerge. :)
--
Rocco Caputo - http://poe.perl.org/
their Calls after they go off.
The many-responses session interaction pattern runs too slowly to
detect a memory leak.
--
Rocco Caputo - http://poe.perl.org/
next
> step?
Install xcode? Make sure you have all your system updates? I don't
know what to say beyond that.
--
Rocco Caputo - http://poe.perl.org/
record, I'm running 10.3.7
No, Event, Tk, and Gtk didn't install with Apple's Perl. Tk builds
successfully with Perl from fink. I think Event does, too. Gtk
doesn't, however.
--
Rocco Caputo - http://poe.perl.org/
nt-dns/blib/lib
/System/Library/Perl/5.8.1/darwin-thread-multi-2level
/System/Library/Perl/5.8.1
/Library/Perl/5.8.1/darwin-thread-multi-2level
/Library/Perl/5.8.1
/Library/Perl
/Network/Library/Perl/5.8.1/darwin-thread-multi-2level
/Network/Library/Perl/5.8.1
/Network/Library/Perl
.
--
Rocco Caputo - http://poe.perl.org/
make test had returned bad status, won't install without force
Time for some "perl -V" action, because I'm developing POE on OS X
now, and I run "make test" before most commits.
--
Rocco Caputo - http://poe.perl.org/
to the
> session, and if you want to have it properly clean up and disconnect,
> don't pass it around.
>
> Rocco, please chime in if I'm wrong.
Here's a previous message where I explained it:
http://aspn.activestate.com/ASPN/Mail/Message/2096709
--
Rocco Caputo - http://poe.perl.org/
On Wed, Jan 26, 2005 at 01:12:08PM -0500, Rocco Caputo wrote:
> I try to reinvent POE::Component at least once a year. The prototypes
> always seem to flush out some fatal flaw, so most people never hear
> about them. Some people hear about them far too much.
>
> This time
ESULT_PARAMETERS_IN_KEY_VALUE_PAIRS,
);
# Fetch one of a call's parameters.
my $parameter = $c->arg(PARAMETER_NAME);
# Flag a Call as received.
$c->receive();
--
Rocco Caputo - http://poe.perl.org/
ten, so there's less
opportunity to cancel or alter the wrong timer by mistake.
Debugging messages (TRACE_EVENTS, particularly) display event IDs.
The diagnostics would be even more confusing if event IDs repeated
often. :)
> Maybe these questions need to be explained in queue API
ould be well.
If they're reading, I hope they offer you a chance to try out some
0day P03 w4r3z. You could provide some preliminary testing before I
get around to it.
--
Rocco Caputo - http://poe.perl.org/
e 215.
>
> Looking at the diff[0] between 0.3003 and 0.3005 it looks like this
> change
[...]
> [0]
> http://search.cpan.org/diff?from=POE-0.3003&to=POE-0.3005#lib/POE/
> Filter/HTTPD.pm
Applied, committed, and 0.3007 shipped to PAUSE. Thanks!
--
Rocco Caputo - http://poe.perl.org/
t;get_active_session()->get_heap();
return unless delete $heap->{"pending_$event"};
$poe_kernel->delay($event, undef);
$poe_kernel->yield($event);
}
1;
It's still meant to be called from the session that will be doing
things.
ExpeditedTimer->do_later("post_query", 5);
ExpeditedTimer->expedite("post_query");
(It's also not tested code, so your mileage may vary.)
--
Rocco Caputo - http://poe.perl.org/
sider when flush() is called to write to a full pipe. It
can't block, so it must return while the driver's buffer contains
data.
A more complete solution would be to check the driver's output buffer
after flush(). If it flushed everything, go ahead and shutdown right
away. Otherwise set a flag in the wheel, and check it after the usual
flush().
--
Rocco Caputo - http://poe.perl.org/
t to be documented in each
subclass.
I briefly considered whether the wheel should guarantee flushing on
shutdown, but I decided against it. Sometimes people may want to shut
down a client regardless of the input waiting for it.
Maybe the shutdown methods need flush/immediate options?
--
Rocco Caputo - http://poe.perl.org/
buffer them for
output. Rather, they convert them and return them right away. The
serialized "things" are sent to the driver for flushing "in a little
while".
Anyway, most wheels have get_driver_out_octets() methods that tell you
how many octets are waiting in the driver to be flushed. I think
that's what you're looking for.
--
Rocco Caputo - http://poe.perl.org/
l need the
> 'doit' and 'shutdown' events to be separate (i.e., combining everything into
> the _start event doesn't work). Is that behavior intentional?
I think it's creating a race condition where your expected behavior
occurs. It seems to be working only by coincidence.
--
Rocco Caputo - http://poe.perl.org/
hits.
Standard operating procedure is to keep the event loop running until
after the last user session has stopped.
I'll need to install WxPerl to run the test program and find out more.
Traditionally I haven't had much luck with WxPerl, though.
--
Rocco Caputo - http://poe.perl.org/
est_info_from_heap();
}
},
}
);
Or something. This is all spur of the moment, and I'm sure the idea
could be refined in a lot of ways.
Maybe a set of base clasess could handle most of the work (request
tracking, response posting, do_everything(), etc.). What would remain
is customizing the object for a particular type of transaction.
--
Rocco Caputo - http://poe.perl.org/
calls?
>
> -Mathieu
Process an HTTPS request. When it's over, open a file, check
fileno(HANDLE), and close it. Loop a few times. An increasing file
descriptor number would indicate a leak.
Thanks for the RT ticket, and the attached test.
--
Rocco Caputo - http://poe.perl.org/
On Sun, Dec 12, 2004 at 02:09:07PM -0900, Leif Gustafson wrote:
> Rocco Caputo wrote:
>
> >The problem is probably in the test program itself. I've had problems
> >with this test on different systems.
>
> I haven't noticed this test failing on previous versio
t really non-blocking, despite the
nonblocking() code in 01_drivers.t. One thing to try is replacing
nonblocking() with $w->blocking(0). You may need to use IO::Handle
first.
--
Rocco Caputo - http://poe.perl.org/
ea where to look to fix this?
If you turn it into a Test::More style test, I'll add it to
Client::HTTP's tests. That'll fairly ensure that the problem gets
fixed before the next release.
--
Rocco Caputo - http://poe.perl.org/
e being run when you try to install and/or test POE.
I suggest flattening your repository.
That's my best guess, anyway.
--
Rocco Caputo - http://poe.perl.org/
;t select a handle 2+ times" error was vague. Thanks to
prodding by Jonathan Steinert, it is now much more specific about
what's going on.
... and stuff like that. Unless I miscounted, 127 (hey, 2^7-1)
changes in all.
--
Rocco Caputo - http://poe.perl.org/
sing it or
sending in some patches if you are.
Thanks for the report!
--
Rocco Caputo - http://poe.perl.org/
On Wed, Dec 08, 2004 at 09:09:28PM -0500, [EMAIL PROTECTED] wrote:
> Large patch to PoCo::Server::HTTP :
Nice! Just a suggestion: It may be useful to Cc: the RT queue for the
distribution. [EMAIL PROTECTED] in this case.
--
Rocco Caputo - http://poe.perl.org/
POE::NFA is implemented correctly. You
can probably find some rather long threads about it in the mailing
list archives. I haven't been plugging it (and demoing it) because
I'm not entirely sure its interfaces are correct. Let me know?
--
Rocco Caputo - http://poe.perl.org/
#x27;event_one');
According to the SYNOPSIS, the proper usage would be
POE::NFA->spawn( inline_states => \%states )
->goto_state( 'start', 'event_one' );
--
Rocco Caputo - http://poe.perl.org/
he task easier should be done as an abstraction outside
POE::Kernel rather than by wedging another timer method into it.
--
Rocco Caputo - http://poe.perl.org/
f you would like the Kernel to
be stricter than this.
--
Rocco Caputo - http://poe.perl.org/
to wait until the 0.31 release.
I'm afraid to fix Tk code without a test case.
Thank you.
--
Rocco Caputo - http://poe.perl.org/
Loop.
A libevent version (perhaps using Event::Lib) would cover many
platforms with one implementation.
How is your kqueue loop coming along, anyway?
--
Rocco Caputo - http://poe.perl.org/
0 posts
Passed, and a tentative deprecation plan has been entered into RT.
--
Rocco Caputo - http://poe.perl.org/
yOtherFreezer::thaw( MyOtherFreezer::freeze(@_));
> > +}
> > +};
>
> Did you intend to double quote @_ here?
The sub should never be called, but @_ may change someday. I've made
it q{} and thrown in a C to be sure the eval works.
--
Rocco Caputo - http://poe.perl.org/
On Wed, Nov 10, 2004 at 08:54:10PM -0400, [EMAIL PROTECTED] wrote:
> Here's a patch against CVS that tests properly and doesn't require another
> module in mylib.
>
> -Philip
[patch]
The patch applied fine.
All tests passed successfuly.
Committed. Thank you.
-
patch to delete
$INC{"$q.pm"} so the require() actually loads a partly-loaded module.
Thanks for the test case and patch. The final versions are applied.
I'm not 100% sure I did the right things to them, so you may want to
take them for a spin.
--
Rocco Caputo - http://poe.perl.org/
on the original test case (but simulating
the XML bits so we don't need them as a dependency). When your
changes pass "make test" (including the regression test), commit them.
Thanks!
--
Rocco Caputo - http://poe.perl.org/
PROTECTED]>. Partial copyright 1999 Philip Gwyn.
If Arthur is watching, he may want to globally replace broken names
and e-mail addresses.
--
Rocco Caputo - http://poe.perl.org/
ROY would fire an event to the session to do
the cleanup. That should guarantee cleanup is done in the proper
context.
Pro: No worries about wheel destruction.
Con: More setup/teardown overhead.
--
Rocco Caputo - http://poe.perl.org/
is paid to
write it). So far you are the most likely candidate. :)
--
Rocco Caputo - http://poe.perl.org/
Proposed POE design workflow, submitted for your consideration. Not a
Nigerian 419 scam, honest.
Proposal by Matt Cashner.
Interpreted and initially documented by Rocco Caputo.
Revised based on feedback from IRC.
Revised based on experience from informally trying it on the list.
POE&#
On Tue, Oct 12, 2004 at 08:31:42PM +0100, Matt S Trout wrote:
> On Mon, Oct 11, 2004 at 06:47:37PM -0400, Rocco Caputo wrote:
> >
> > Things to try:
> >
> > - Try a different version of Perl on the affected systems.
> > - Gather good data points to rule o
when the author is
unresponsive?"
http://www.cpan.org/misc/cpan-faq.html#How_maintain_module
--
Rocco Caputo - http://poe.perl.org/
On Mon, Oct 11, 2004 at 07:46:54PM -0700, Michael Nino wrote:
> Rocco Caputo wrote:
> >On Fri, Oct 08, 2004 at 02:05:40PM -0700, Michael Nino wrote:
> >>
> >>I am investigating what I should do? Seems trivial for some who already
> >>knows POE and Perl m
release as time goes on
and new requirements surface. The easiest way to avoid that is to get
the existing requirements out of the way before things come up.
Anybody want to expedite 1.0 by contributing a test program or some
documentation? There's plenty to go around...
--
Rocco Caputo - http://poe.perl.org/
301 - 400 of 1064 matches
Mail list logo
