-
Notifications
You must be signed in to change notification settings - Fork 26
/
Component.pm
50 lines (31 loc) · 1008 Bytes
/
Component.pm
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
# $Id$
# Copyrights and documentation are after __end__.
package POE::Component;
use strict;
use Carp qw(croak);
sub new {
my $type = shift;
croak "$type is not meant to be used directly";
}
1;
__END__
=head1 NAME
POE::Component - POE Stand-Alone Sessions
=head1 SYNOPSIS
Varies from component to component.
=head1 DESCRIPTION
POE components are sessions that have been designed as stand-alone
modules. They tend to be interfaced through POE::Kernel::post() or
call(), but this is not a formal convention.
The POE::Component namespace was started to provide a place for others
publish their POE modules without requiring coordination with the main
POE distribution.
=head1 SEE ALSO
The SEE ALSO section in L<POE> contains a table of contents covering
the entire POE distribution.
=head1 BUGS
The POE::Component namespace should probably be coordinated, but who
has time for that?
=head1 AUTHORS & COPYRIGHTS
Please see L<POE> for more information about authors and contributors.
=cut