On Wed, 27 Jun 2001 [EMAIL PROTECTED] wrote:
> Not having session monitoring means that I can't robustly implement IKC
> publish/subscribe. So, I will be removing this feature from IKC in the
> next major release (version 1.0) and moving it to some object layer.
> Version 1.0 will also move the pre-forking code and babysitting code
> elsewhere and refactor the negociation phase/protocol. Yes, this will
> break a huge pile of code, but either a) backward compatibility hacks will
> be avaiable, b) can stay with a 0.x version or c) tough, you want to use
> 1.x you have to use the object layer. IKC will be back to what it was
> originally should have been: getting events from kernel A to kernel B.
is this going to break monitor and what not?
/me crosses fingers
--------
Matt Cashner
Web Applications Developer
The Creative Group (http://www.cre8tivegroup.com)
[EMAIL PROTECTED] | Codito, ergo sum
