T
Thomas Mercer-Hursh
Guest
It just seemed to fit with your architectural discussions. Anyway, it reminded me of my work with Forte in the mid-90's. Everything was written as a service and one deployed those services across a network of nodes via configuration, i.e., without new programming. Multiple services could be on each node. Unlike AppServer, a service was running for the duration and its location was published so that a client or other service who needed what it provided could look up the service and make a connection to it. Any one service could thus have a large number of current connections, but the service itself was a multi-threaded process, so the service could listen on all the connections and spawn a thread to do work. This enabled such things as a client requesting some data and registering an interest in that data. If the data changed while the client was still interested, the service would send a data changed message to the client and the client could then decide whether it wanted to request a fresh copy.
Continue reading...
Continue reading...