At 11:20 AM 15-05-00 -0700, you wrote:

>Easily done with the current architecture:
>
>1. Isql posts an INSERT/UPDATE/DELETE or calls a procedure.
>2. Procedure or trigger posts an EVENT.
>3. Server-side process listening for the EVENT leaps into action,
>performing server-side business tasks without having to worry about network
>latency etc.
>
>I think this would be far more useful if we extend the EVENT mechanism to be
>able to return data instead of just the event name. But we all wanted that
>capability anyway.
>
>Bill Karwin

Amen to that. EVENT is a wonderful, unexploited stub of opportunity.

Helen

http://www.interbase2000.org
___________________________________________________
"Ask not what your free, open-source database can do for you,
but what you can do for your free, open-source database."
(J.F.K.)