Something I mused on this morning was the possibility of wrapping web services as actors. This opens up a few possibilities:
The ability to scale up from a single VM to multiple VMs spread across a network, with little change to your actor client code. Basically all you'd have to do is make sure your request and response messages are all serializable, vs on a single VM where you can use const objects regardless of serializability.
This could be an elegant way of adding actor functionality to JavaScript in the browser.
I haven't thought about this too deeply but thought I'd throw the idea out there for anyone interested.
brianFri 2 Jul 2010
I've given some thought to something like that too. Basically you should be able to use network aware actors in place of a real actor:
A => B
A => NetClient => NetServer => B
Where NetClient and NetServer are just actors that serialize messages across some network link. I think it could even be packaged up into some nice standard pod for reuse (where NetServer just plugs into the URI space via a WebMod).
qualidafial Mon 28 Jun 2010
Something I mused on this morning was the possibility of wrapping web services as actors. This opens up a few possibilities:
constobjects regardless of serializability.I haven't thought about this too deeply but thought I'd throw the idea out there for anyone interested.
brian Fri 2 Jul 2010
I've given some thought to something like that too. Basically you should be able to use network aware actors in place of a real actor:
Where NetClient and NetServer are just actors that serialize messages across some network link. I think it could even be packaged up into some nice standard pod for reuse (where NetServer just plugs into the URI space via a WebMod).