This one has the goodies! One thing I've been thinking about, and need
YOUR feedback is parameter passing. Currently, IKC only passes ONE
argument, unless you use a Proxy session via the subscription mechanism.
This seems very limiting... I had started to do it, when i realised that
IKC/call expects the callback name *after* the param. So, either I break
IKC/call or I make the callback name the last param.
$kernel->post('IKC'=>'post', "poe://Kernel/Session/Event,
...many params here...);
$kernel->post('IKC'=>'call', "poe://Kernel/Session/Event,
...many params here..., 'poe:/me/Callback');
Anyone see a reason this would break there code?
-Philip
0.13pre7 20 June 2001
- Added IKC/published, for sungo
- Fixed doco a bit
- Added a prereq for POE 0.1403
0.13pre6 6 June 2001
- ADDED TESTS!
Woot woot! Now make test verifies something meaningful.
- No longer thunking sessions that don't publish any states
- Finally did unsubscribe... turns out retract was available all along
- Added IKC::{Client,Proxy,Responder,Server}->spawn method, to
be used in favour of create_ikc_*mumble*
- Added IKC/post2 .... internal use only
- Added FlushedState handler to IKC::Channel. This way, wheel isn't
destroyed until all data is flushed. This means you can post
events to remote kernels and then IKC/shutdown right away. I hope.
