Talk:AssetServer

From OpenSimulator

(Difference between revisions)
Jump to: navigation, search
(Capability Cookies)
(== Capability Cookies ==)
Line 6: Line 6:
  
  
== == Capability Cookies == ==
+
== Capability Cookies ==
  
 
I like the idea of capabilities being packaged as cookies, that seems much more palatable than (ab)using the URI.
 
I like the idea of capabilities being packaged as cookies, that seems much more palatable than (ab)using the URI.
 +
--[[User:Awebb|Awebb]] 06:45, 9 October 2008 (PDT)

Revision as of 06:45, 9 October 2008

Metadata

As far as the specific serialization format goes I don't have much of a preference. Ideally, a robust asset server would support multiple serialization formats such as XML, LLSD XML, JSON, binary, etc. Where it gets tricky is with the higher level representation. There are two schools of thought: strongly typed data and weakly typed data. Linden Lab's UDP, Google's Protocol Buffers, and Facebook's Thrift are examples of strongly typed protocols. Linden Lab's structured data and most XML schemas are examples of weakly typed data.

Should systems like the asset service focus on strongly or weakly typed data? Are there compelling reasons to choose one direction over the other? --Jhurliman 15:59, 6 October 2008 (PDT)


Capability Cookies

I like the idea of capabilities being packaged as cookies, that seems much more palatable than (ab)using the URI. --Awebb 06:45, 9 October 2008 (PDT)

Personal tools
General
About This Wiki