P is for Practical | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
My actual goal is the implementation of a peer-to-peer framework. On top of this framework is a central executive node. Nodes are servers (database servers, analysis servers, collaboration servers etc.) and clients (desktop computers). The peers communicate with each other using messages (xml) and chat services. You see, events are the basis for the inter-node activities. So, this is the reason for POE, the multitasking and networking framework for Perl (...) POE is a framework for cooperative, event driven multitasking in Perl. Other languages have similar frameworks. Python has Twisted. TCL has "the event loop". .
Yes. Imagine, one user triggers a job from a client node. The central executive processes or possibly forwards the execution request , tracks and feeds back the output to the requesting node. Other nodes/ users are informed about the execution (utilizing chat services). Furthermore, the execution request has been enqueued in the central executive's message queue. Users can send read requests. If processing is already done, they simply receive the output. If processing is not done, yet, they see the same (following) output of the process.
Exactly. It is clear now, that the executors and output recipients reside on different network nodes.
No.
Somehow. The central executive node actually triggers the request, receives the output and broadcasts the output.
Somehow. See the above comment.
This is exactly what I want to achive.
What is the best approach if you understand my goals? In reply to Re^2: POE and Win32::Process control
by m-rau
|
|