A '''remote interpreter''' is at the heart of the [concurrency
concepts%|%concurrent] systems available for Tcl.  This page contains a list of
those systems. 



** Independent State **


   [hubs remote interp]:   has an interface emulating `[interp]`, including the capability of creating aliases in the slave which call back to commands in the master.

   [mkextensions%|%mkrinterp]:   A remote interpreter is created and used like a regular Tcl interpreter, but resides in fact on any host that is running an rinterp server.

   [Remote Script Execution]:   An example implementation  of a client/server arrangement to execute command in a safe interpreter.

   [Simple remote Tk execution - distanciel]:   

   [pcom]:   


** Shared State **

[Tequila]: Uses [trace%|%traces], [fileevent%|%fileevents] and [socket%|%sockets] to create distributed [array]s, i.e. arrays whose content is shared between several applications and where changes are automatically distributed to them all. It makes use of a central server. It does have the advantage that applications can be built using arrays for data storage, and separated into client/server components with only a few additional lines of code.

   [http://cfa-www.harvard.edu/~john/msg%|%MMTI Message Passing Protocol and] [API]:    interface that is used to operate F5 instrumentation at the [http://cfa-www.harvard.edu/mmt/%|%MMT Observatory].  Very similar to [Tequila] above but operates on global variables.  It supports publish, subscribe of values and commands. It includes synchronous, asynchronous and unacknowledged messages.  Clients persistently reconnect to servers and reestablish thier subscription states automatically.  It works very well and is used to tie dozens of hardware and software control functions at the MMT Observatory together. -- [JBR] (updated by [escargo]).
 
   [Linda]:   (note that [Todd Coram] cobbled together a Tuplespace%|%tuple space] in a few lines of [incr Tcl]), ...



<<categories>> interp | concurrency concepts