Hole in one! :) That's exactly what I meant: client-controlled animations with the data that drives those animations stored such that you can log in from multiple computers and still have your animation sets available and (optionally) linked with outfits.
Ricky Cron Stardust PS: For the record, I'm one of those annoying people who have stuck with the "duck walk" because I couldn't care less. That said, this topic hit me in one of my favorite themes: system design - hence my participation. :) On Tue, Apr 17, 2012 at 9:36 AM, Stickman <stick...@gmail.com> wrote: > > What kind of server-side do you (and others!) really mean? It's been > > done the way it currently is (or rather, historically has been) for so > > long that I'm actually at a loss as to what the server has to do with it > > other than telling other clients "such-and-such is playing this > > animation." It's a little difficult for me to fathom what client-server > > interaction would be required beyond this. > > > > Maybe I'm just being dense, but beyond a slightly lightened script load > > on the server I honestly can't think of any particular advantage to > > doing it client-side, or what doing it with a client-side component > > would need partner components on the server for. > > > > Maybe it's just me. > > The entire point of client side AOs is to avoid the server. So yes, it > seems odd it would use the server. > > However, if no part of the server is used, the clientside AO data is > stored clientside. Log into your account from another computer, and > you no longer have your AOs. > > What makes sense is having the client-controlled AO data be stored on > the server so it can travel around with your login. Once you log in, > it's transmitted to the computer and acts and executes on the > clientside, with all the clientside benefits, with the added advantage > of being "backed up" on the server. > > The natural continuation of this idea is having it "paired" with > existing outfits, as an inventory object or some other identifier (I > vote for a "gesture" like window where you can assign pre-built > clientside AOs to specific outfits) so when you change outfits, you > can also magically change AOs without effort. > > Did I miss anything, or is this what we're getting at with this > ridiculously huge discussion? I admit I haven't been reading > everything. > > Stickman > _______________________________________________ > Policies and (un)subscribe information available here: > http://wiki.secondlife.com/wiki/OpenSource-Dev > Please read the policies before posting to keep unmoderated posting > privileges >
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
