Seems like they have yet another project cooking – ripley project.
We propose Ripley, a system that uses replicated execution to automatically preserve the integrity of a distributed computation. Ripley replicates a copy of the client-side computation on the trusted server tier. Every client-side event is transferred to the replica of the client for execution.
Ripley prevents a malicious user or remote hacker from altering the behavior of code running inside a Web browser by creating an exact copy of the computational environment and running that copy on the server. Ripley then sends all of the user’s actions, including mouse clicks, keystrokes, and any other inputs, in a compressed “event stream” from the client to the server. This stream is run through the cloned client application on the server, and the behavior of that virtual doppelganger is compared to that of the application running on the user’s browser at home. If there are any discrepancies, Ripley disconnects the client.
It is very important to carefully analyze available tools and to place one self in the market. At the moment jsc is not in the business of replicating client side business logic in the server side. Yet jsc is capable of that. I will revisit this idea in the future.
If jsc solution were to implement the idea then:
- Server side business logic could run on PHP
- Server side business logic could run on Google App Engine Java
- Server side business logic could run on ASP.NET
- Client side business logic could run on flash
- Client side business logic could run on java
Update: Come to think about it jsc solution could pursue another goal of automatic synchronization of client applications via stratus which just recently got multicast support.
- HTML DOM in Google App Engine via Native Client?
- The client CPU is cheaper!!!
- C++: A language for next generation web apps
- See this talk
- Orleans by Microsoft Research
- Coign by Microsoft Research
- Microsoft TypeScript