Bot-ChatBots
view release on metacpan or search on metacpan
while in this case you might have longer running tasks. This can be
addressed in different ways, one of which might be to split your
pipeline into chunks, and decouple these chunks via some queuing
mechanism.
Apart from this, the suggested way to use Bot::ChatBots elements is
sticking to the Data::Tubes way of work: define your pipelines, reuse
already-available tube builders or code your own adhering to the
(simple) tube interface.
BUGS AND LIMITATIONS
Report bugs either GitHub (patches welcome).
SEE ALSO
Bot::ChatBots::Telegram should be the first implementation of a backend
(for Telegram).
AUTHOR
lib/Bot/ChatBots.pod view on Meta::CPAN
addressed in different ways, one of which might be to split your pipeline
into chunks, and decouple these chunks via some queuing mechanism.
=back
Apart from this, the suggested way to use Bot::ChatBots elements is
sticking to the L<Data::Tubes> way of work: define your pipelines, reuse
already-available tube builders or code your own adhering to the (simple)
tube interface.
=head1 BUGS AND LIMITATIONS
Report bugs either GitHub (patches welcome).
=head1 SEE ALSO
L<Bot::ChatBots::Telegram> should be the first implementation of a backend (for
Telegram).
=head1 AUTHOR
lib/Bot/ChatBots/MojoPlugin.pod view on Meta::CPAN
=back
=head2 B<< instances >>
my $aref = $obj->instances;
$obj->instances($array_ref);
Accessor for defined instances, stored in an array reference.
=head1 BUGS AND LIMITATIONS
Report bugs either through RT or GitHub (patches welcome).
=head1 SEE ALSO
L<Bot::ChatBots>.
=head1 AUTHOR
Flavio Poletti <polettix@cpan.org>
( run in 0.267 second using v1.01-cache-2.11-cpan-4d50c553e7e )