Difference between revisions of "Structural Design Overview"
Tao Takashi (talk | contribs) |
Which Linden (talk | contribs) (→Made decisions: Chttp isn't that far along) |
||
| Line 25: | Line 25: | ||
* It will all be based on [http://en.wikipedia.org/wiki/Representational_State_Transfer REST] | * It will all be based on [http://en.wikipedia.org/wiki/Representational_State_Transfer REST] | ||
* | * [[Certified HTTP]] will be used where appropriate (exactly-once messaging between reliable hosts). Implementation is ongoing. | ||
* [[Capabilities]] will be used | * [[Capabilities]] will be used | ||
* [[LLSD]] will probably stay on not be changed to JSON. According to Linden Lab this should be no problem as there is a library for most languages to handle LLSD. | * [[LLSD]] will probably stay on not be changed to JSON. According to Linden Lab this should be no problem as there is a library for most languages to handle LLSD. | ||
Revision as of 12:19, 15 September 2007
In Meeting 1 Zero Linden was giving a small overview of how Linden Lab is thinking about a new architecture for the Second Life grid.
Today and Tomorrow
First a slide on how things work today:
Today the viewer only connects to the region and the region keeps track of everything and acts as a proxy to the central databases. With the numbers envisioned in Project Motivation the central servers will not be able to cope with that.
The solution Linden Lab sees is to divide the structure into an Agent Domain and a Region Domain, each of them handling the components they are named after. Moreover there are some more central services such as Identity, Location, Currency and Search and there might be the case that multiple domains need to work together.
Made decisions
- It will all be based on REST
- Certified HTTP will be used where appropriate (exactly-once messaging between reliable hosts). Implementation is ongoing.
- Capabilities will be used
- LLSD will probably stay on not be changed to JSON. According to Linden Lab this should be no problem as there is a library for most languages to handle LLSD.
Final example setup
If all this is implemented it might look like this in the end.