agents

This enables user agents to verify that the server is willing to serve the script that opened the connection.

It would mean serializing all the updates, but you could use fine-grained agents like I'm using fine-grained atoms.

You could turn agents into actors by limiting what they respond to, and you can turn actors into agents, by having an environment actor and agent actors.

The event calculus could be used to specify the behavior of the agents instantiated by ethereum smart contracts.

The problem is in difference between URL and URI, because URIs are hosted/registered directly on user computers/agents, so for example it's not possible to take advantage of javascript/css.

An agent can broadcast a message through the environment, and any other agents who notice can respond.

Because it is not a table, it displays in a tabular fashion (for certain user agents).

Just to be clear: V-Männer or V-Personen are snitches and not undercover agents of the Verfassungsschutz.

Any experienced Clojure people care to comment on why atoms were used instead of agents?

Build out our client side using React and Backbone, while keeping a sharp focus on the customer experience for our agents and consumers.

I would go out on limb and say that software agents will be the next big thing.

I have zero experience with agents, can someone explain how different this language is from Erlang?

Agents launch the update function in a separate thread, which seems a bit much for incrementing a counter.

Companies which explicitly hold other people's money are usually held to higher standards in holding it (Solicitors, Banks, Estate Agents, etc).

Agents interact with their environment while actors interact with other actors.