Distributed Event Model

Get Started. It's Free
or sign up with your email address
Rocket clouds
Distributed Event Model by Mind Map: Distributed Event Model

1. What is an "event"?

1.1. Large number of small exhibits on a central theme

1.2. Exhibits may be subgrouped

1.2.1. Charity Clothes Sale -> Hats / Shoes / Frocks

1.2.2. Victorian History -> Political / Social / Technological

1.3. Usually time-limited

1.3.1. Is this because of the resources necessary?

1.3.2. What is the point of time limits, if there is no need to have them apart from if enough of the exhibits can't carry on?

1.3.3. "Critical mass" of exhibits needed to say that an event is open

1.3.3.1. Below this limit, it is effectively "closed"

1.3.3.2. Exhibits can be moved/rehoused/restarted elsewhere

1.3.3.3. Allows for a "rolling event"

1.4. Can be publicised with a central entry point

1.4.1. This doesn't have to be a physical place

1.4.2. Could just be a list of sims, folder of landmarks, or device

1.5. Easy to move between exhibits and see what exhibits exist

1.5.1. Normally done by geographical location with traditional model

1.5.2. Simply move to other exhibits

1.5.2.1. Quick

1.5.2.2. Easy to see what exhibits exist

1.5.2.3. Easy to bypass uninteresting ones and move to something else

1.5.2.4. With increasing event size, the above becomes harder though.

2. Current problems

2.1. Events in one sim are laggy

2.1.1. Puts visitors off.

2.1.2. Sometimes, the whole thing just dies.

2.1.2.1. Unpredictable

2.1.3. Requires lag-maintenance

2.1.3.1. Restricts what people can build

2.2. Require permissions and awkwardness

2.3. Impermanent - time available for is determined by sim owner/finances, rather than by individual.

2.4. All exacerbated by having contiguous sims

2.4.1. More cost

2.4.2. More lag (overlooking other sims)

2.5. Expensive or reliant on sponsors

2.5.1. Getting the money together for full sims, even rental, in a group is awkward

3. Proposal

3.1. Exhibits are physically present in any location - not required to be in a particular location

3.2. Core concept

3.2.1. Independent database/list of exhibits and their locations

3.2.2. This is the core of the event, rather than the core being their physical presence in a parcel and the database being a description of that

3.3. Movement between exhibits

3.3.1. Must be done via landmarks/llMapDestination.

3.3.1.1. Slightly awkward - but no more awkward than having to TP within a large event.

3.3.2. Descriptions etc can be added to the database to give people an idea of what the event is.

3.3.2.1. Textual description

3.3.2.2. Tags

3.3.2.3. Images

3.3.2.3.1. Textures

3.3.2.3.2. Links to web images

3.3.2.4. Further information

3.3.2.4.1. Notecards

3.3.2.4.2. Links to web pages

3.3.2.5. All this can be delivered via a HUD or attachment or static item.

3.3.3. Mechanisms

3.3.3.1. Static item in exhibit

3.3.3.1.1. Allows movement between this and other exhibits

3.3.3.1.2. Registers and maintains exhibit with database

3.3.3.1.3. Maybe...

3.3.3.2. General HUD or attachment

3.3.3.2.1. Basically similar to static item

3.3.3.2.2. Does not create a new exhibit (obviously)

3.3.3.2.3. Must work out which exhibit it is currently in

3.3.3.3. Web pages

3.3.3.3.1. Can have above functionality for moving directly to a parcel via secondlife:// links

3.3.3.3.2. Sub-pages for exhibits?

3.3.3.3.3. Given the inworld browser, might eliminate the need for a HUD at all

3.4. Time limit

3.4.1. It _can_ be time limited, but it would be done deliberately.

3.4.2. As long as people have their builds up, the event can go on.

3.4.3. On the other hand - if they lose their builds for some reason, the event stops

3.5. Parcel vs sim(s)

3.5.1. Good

3.5.1.1. Not dependent on having obtained a large space, which is always difficult

3.5.1.2. Reduces lag, if places are separated

3.5.1.3. Does not restrict content on a lag basis

3.5.1.3.1. If you have an empty enough sim to build in, you can make your exhibit as script- and texture- and sculptie-heavy as you like

3.5.2. Bad

3.5.2.1. Requires that people have access to enough space to build on

3.5.2.1.1. The main problem for SL builders

3.5.2.1.2. "Land donations"?