POE::Component::FunctionBus - Easily scalability
Version 0.01
The entire point of this module is to make a very fast/easy interface for attaching internal and even external functions to a common standardized serialization bus. (The serialization used is not enforced)
This module is the forerunner for an upcoming protocol that is in RFC, as the author of the same protocol I have decided to race ahead and make something from its fundamental core principles to solve some issues I have in the present.
Simply put you can publish functions over a common protocol (not neccesarily just in perl) and instead of them being controlled by any type of namespace, they are infact simply functions on a bus so for scalability of that expensive processing function, you can attach as many workers as like.
This does however mean that very large complex tasks should be split down into as small of a set of work functions as possible, so that they can be more easily distributed amongst multiple processes.
But no one writes large heavy monolthic 'evil' functions anymore, right?
To be considering using this type of distributed work network you should also remember that it is rather dependant on code enacting postback type behaviour, rather than block-and-return.
Not that you could not use block-and-return it would just well, be rather resource hungry and not very scalable. If you do have a_function() that takes 8 days to run, consider wrapping it in a service that responds that it is busy or so. That way you can have multiple nodes providing that service.
Perhaps a little code snippet.
use POE::Component::FunctionBus; my $options = { } my $node = POE::Component::FunctionBus->new($options); $node->offer()
There are no exports for this module
These are for instanciating connecting nodes
Create a new connection object, by default this will act as both a server and client, it also by default binds 0.0.0.0/IPV4_ANY on port 10101(TCP) as well as af_unix:/tmp/functionbus.PID.sock (PID here meaning the literal PID that perl is using)
These are primarily functions that can be called on the resultant POE::Session returned from an initilizer (documented above), in the spirit of non blocking processing you should really use these as little as possible
These are binds to anonymous POE::Kernels that post into the primary session, as of such they do not return anything directly but some may allow callbacks.
Networks are generally dynamically created within the scope of a set of working nodes however this in its self is given a unique id, just incase there happens to be more than one network running.
This value can be set in the initilizer.
Paul G Webster, <daemon at cpan.org>
<daemon at cpan.org>
We don't have these!
Incase we are wrong though report any bugs or feature requests to https://github.com/PaulGWebster/p5-POE-Component-FunctionBus/issues.
I will be notified, and then you'll automatically be notified of progress on your bug as I make changes.
You can find documentation for this module with the perldoc command.
perldoc POE::Component::FunctionBus
You can also look for information at:
Github: Authors repository
https://github.com/PaulGWebster/p5-POE-Component-FunctionBus
AnnoCPAN: Annotated CPAN documentation
http://annocpan.org/dist/POE-Component-FunctionBus
CPAN Ratings
https://cpanratings.perl.org/d/POE-Component-FunctionBus
Search CPAN
https://metacpan.org/release/POE-Component-FunctionBus
Rocco Caputo is <rcaputo@cpan.org>. POE is his brainchild. He wishes to thank you for your interest, and he has more thanks than he can count for all the people who have contributed. POE would not be nearly as cool without you.
Except where otherwise noted, POE is Copyright 1998-2013 Rocco Caputo. All rights reserved. POE is free software; you may redistribute it and/or modify it under the same terms as Perl itself.
This software is Copyright (c) 2019 by Paul G Webster.
This is free software, licensed under:
The (three-clause) BSD License
This section is because this module is under heavy development, really its just notes to my self on what I am planning to do - examples and other bits and peices. (or total junk)
Anything in this section should never be reffered to as once this module hits release this section will vanish.
make it so /var/functionbus.pid.sock (pid representing the master perl process) is contactable
Write down precisely what is required to talk on one of these networks so other people have half a prayer of using it in other languages, maybe write a csharp module? maybe kick python/java friends to do the same hmmm
Start a session and setup the initial enviroment
Called when the main POE::Session stops ... tidying up
1 POD Error
The following errors were encountered while parsing the POD:
=cut found outside a pod block. Skipping to next block.
To install POE::Component::FunctionBus, copy and paste the appropriate command in to your terminal.
cpanm
cpanm POE::Component::FunctionBus
CPAN shell
perl -MCPAN -e shell install POE::Component::FunctionBus
For more information on module installation, please visit the detailed CPAN module installation guide.