[sldev] Direction for Snowglobe 1.3

Aleric Inglewood aleric.inglewood at gmail.com
Wed Dec 2 03:38:45 PST 2009


Hmm, actually - this is not true. What would be needed is just that this mask
is added to the messages about actual attachments, between the client
and the server. The server only needs to remember the mask for each
actually attached attachments per agent and does not have to communicate
about that with others (it's a local thing).

The change is really very minimal thus. That approach would require the
viewer to remember this mask itself (locally, on disk) for every attachment
(also those in the inventory); but at least we have full control over THAT.

The disadvantage of this approach is that the mask would get lost
when an object is transfered; but that isn't really a problem imho: it's
really pretty personal configuration data, every user should just choose
his/her own setting.

[The mask would tell the viewer and server when to remove a given
attachment when another attachment is being added: ie, if on attachment
point X there is an attachment with a mask 4, and a new attachment
is added with mask 3, then both will be attached. And if then another
attachment is added with mask 5, then the previous two would be
removed because 5 & 4 != 0 and 5 & 3 != 0].

Another disadvantage is that every client would have support seeing
multiple attachments on a single attachment point, or the server would
have to start doing 'translations' (make one a temporary single object
of the several attachments on a single point, and "attach" that towards
the rest of the world).

On Wed, Dec 2, 2009 at 12:26 PM, Aleric Inglewood
<aleric.inglewood at gmail.com> wrote:
> Hi Merov,
>
> what about multiple attachments per attachment point?
>
> The problem is that the correct way to implement this needs
> server-side patches too.
> That is not a reason not to continue, I just mention it to make clear
> that this is NOT
> a snowglobe thing.
>
> I regret it that we don't have a good communication link with ALL LL developers,
> only with the handful that is working on snowglobe, or maybe I'm just missing
> an overview. Is there anyone here who could say: Ok, lets change the
> server-client
> protocol?
>
> ------------
>
> As for the implementation, what is needed is a new mask (at least 16 bit,
> but 32 would be nice) that is part of every attachment and which can
> be changed by the user EVEN on no-mod objects! I lack the knowledge
> of the server code to know if it's at all possible to add/have a modifiable
> variable on a no-mod object ...
>


More information about the SLDev mailing list