Re: Networking in Prolog - a survey

On Wed, 21 May 2008 10:49:23 -0700 (PDT), Alessio Stalla

I think the current architecture (with small modifications) could
allow to run the event handler code with a separate prolog stack, so
there's no need to make the interpreter loop synchronized. My main
concern is not multithreading per se, but giving the user access to a
full-blown threading api in prolog, which would require some effort.
If I limit the handling of threads to be only on the Java side, I can
avoid that concern for now. Of course that doesn't really solve the
problem in general since the code triggered by events will eventually
have to cooperate with code running on the main thread, but in my
limited scenario, in which event handling will simply be some limited
processing of the received data and possibly an assert to augment the
current theory, that problem isn't influent.

The above is such clever that I din't undrestand single word...
But.,.. Have you seen Prolog Beans and Linda in SICStus Prolog?...

A.L.
.