Top 10 Limitations & Restrictions of New HTTP-in Objects Coming to Second Life by July 15
Second Life objects will finally be able to receive HTTP requests while reducing the load on servers. By July 15, 2009 a full deployment of Second Life Server 1.27 and HTTP-in should be available. There are a ton of great uses for this mainly for controlling objects in Second Life from outside of the virtual world. It is also another step closer to making Second Life more of a browser based technology. The most immediate uses will be for realworld to virtual world communication such as with SLim and other types of messaging, voice over ip, chat, and integration with APIs and services such as twitter and facebook.
With Great Power Comes….Great Limitations: Top 10 Limitations and Restrictions of HTTP-in Objects in Second Life:
Of course with this great new feature come some rather restricting limitations and rules:
1. There will be URL limits per region and split by land ownership
2. URLs will be temporary
3. A maximum of 38 URLs per resident can be used (this also means 38 attachment points total)
4. HTTP requests are limited to 2 kb in the body (wow really? Is anything that small 2 kb?)
5. Headers will be limited to 255 bytes (even smaller)
6. Response sizes will likely be limited
7. Per script limit of 64 flight requests
8. Speeds may be throttled
9. Returned data is only in text/plain; utf-8 format
10. URL limits are the same as the prim limits
Read more here
