bit more cleanly shared and the process of resolving zones and scenes and the
various fiddling done during a scene move can be more easily grokked.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@363 c613c5cb-e716-0410-b11b-feb51c14d237
new pattern of having a Provider interface which is implemented by a Manager or
other server-side entity.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@358 c613c5cb-e716-0410-b11b-feb51c14d237
a new server and reissue its request, which it, in theory, now does.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@354 c613c5cb-e716-0410-b11b-feb51c14d237
I'm going to assume that this one is ok to change to 0, because that's
what a body's sceneId is going to be before they're ever placed in a scene.
(Which is why 0 is a much better default value.)
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@312 c613c5cb-e716-0410-b11b-feb51c14d237
They *are* just updates, but if it's ok for them to not load then a
game-specific scene repository needs to make that decision and just
return a blank update list rather than throwing an exception.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@68 c613c5cb-e716-0410-b11b-feb51c14d237
about the current scene model instead of informing them that the version
they have is OK. It's not ok!
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@25 c613c5cb-e716-0410-b11b-feb51c14d237
extensions to the distributed environment provided by Narya.
git-svn-id: svn+ssh://src.earth.threerings.net/vilya/trunk@1 c613c5cb-e716-0410-b11b-feb51c14d237
Michael Bayne