Re: [vwrap] Statements of Consensus. Flexibity First.

Morgaine, we mooted your hash-based idea. This does nothing to help 
implement asset services. The only significant point you made is some 
expression for optimization, not correct functionality, which is needed 
first

As for your other two, we can summarize those with public resources and 
flow (forward/reverse). Any more specific network topology than that 
only makes it harder to address. The only thing to worry about is 
already custom resources that overlap with newer public resources.

Morgaine wrote:
> On Tue, Apr 5, 2011 at 5:38 PM, Dzonatas Sol <dzonatas@gmail.com 
> <mailto:dzonatas@gmail.com>> wrote:
>
>
>     Do you think we are ready to implement some asset services now,
>     with/without complete documentation?
>
>     What more do you think is needed?
>
>
> Two or three things seem to be needed:
>
>     * Defining the asset addressing concept is an extremely important
>       matter, almost certainly the most important matter of all,
>       because that determines how robust and scalable our worlds will
>       be.� I've already examined alternatives for that in some depth,
>       and the design with the best engineering properties so far seems
>       to be universal hash-based addressing.� I first described that
>       approach on the list here ---
>       http://www.ietf.org/mail-archive/web/vwrap/current/msg00463.html
>       , and referred to it in various subsequent discussions.
>
>     * Defining the data flows between regions, clients, and asset
>       services and which parameters control the flows needs to be done
>       before a test asset service can be implemented.� Without that,
>       an asset service is just a network-accessible storage service,
>       not an asset service in the VWRAP sense.� Network storage
>       services exist already, so just implementing one of those would
>       not advance VWRAP.
>
>     * We need to examine how various deployment patterns will use the
>       asset services, and how the /multiple/ asset services that
>       interop introduces are handled.� I am working on this currently.
>
>
> None of the above is particularly hard.� I think it won't be long 
> before we have a scheme worked out and are ready for some 
> implementation work.
>
>
> Morgaine.
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> vwrap mailing list
> vwrap@ietf.org
> https://www.ietf.org/mailman/listinfo/vwrap
>   

-- 
--- https://twitter.com/Dzonatas_Sol ---
Web Development, Software Engineering, Virtual Reality, Consultant