Multi-Process Client VAG -- draft

From Second Life Wiki
Revision as of 04:10, 7 November 2007 by Morgaine Dinova (talk | contribs) (New page: {{Template:AWG_NavBox}} :# '''This is a pre-draft of the draft''' : This is an early draft so scope and focus are still fairly open. Please add comments to the [[Talk:Multi-Process Client...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
  1. This is a pre-draft of the draft
This is an early draft so scope and focus are still fairly open. Please add comments to the Talk:Multi-Process Client VAG if you have slightly different concerns so that we can try to converge on a common viewpoint. This discussion could also expose other similar VAGs that are needed in this area.

Purpose

The Multi-Process Client Viewpoint Advocacy Group exists to provide input to the overall system archtecture design process in those areas where client-side functionality needs to evolve to track server-side changes.

More specifically, the Multi-Process Client VAG is concerned with identifying the key server-side changes that impact on the client, proposing at least one reference design for the client that can address all the expected changes, and assisting with the design and implementation of such a reference client. This work is expected to generate feedback in the opposite direction as well: a range of client-based Use_Cases will be examined in this VAG and used to generate requirements for the system architecture, particularly in the areas of scalability and interoperability.

As is evident from its name, this Multi-Process Client VAG has predefined one specific aspect of the required client, namely the change from the monolithic process structure of the original Linden client to a multi-process one. This will be discussed and justified in detail below, but it is not exclusionary: other client-oriented viewpoint groups may proceed along different lines.

This is a technical VAG.

See the Architecture Working Group and the Viewpoint Advocacy Groups for more information.

Areas addressed by this viewpoint

  • Server-side APIs visible from the client.
  • Scalability of the combined client and server systems from a client-side perspective.
  • Interoperability of grids and worlds from a client-side perspective.
  • Client diversity and its impact on client structure.
  • Designing clients for extensibility.
  • Use of clients as test tools.
  • Harnessing the power of community for rapid client evolution.

Areas not addressed by this viewpoint

  • Server-side details that are not visible from the client.

Multi-Process Client VAG Glossary

See Architecture Working Group Glossary for terms not defined here.

Source of Viewpoint

No existing sources for this viewpoint have (yet) been sought. This viewpoint is however highly reusable, and therefore existing sources are very likely to exist and should be investigated.

General concerns addressed by this viewpoint

TBD

Specific concerns within this viewpoint

Here we define the specific concerns relevant to event scalability.

Use Cases

Proposals and Analysis

Organization

Joining

Anyone with an interest in this Viewpoint is welcome to join. You should join the AW_Groupies group in Second Life.

In world meetings

This group is currently active on a continuous basis, communicating over group and friend/calling-card IM and via wiki. We will also endeavor to meet at least once a week in-world, or more frequently if desired.

Members are active on the wiki and in the SLDEV mailing list.

Meetings Schedule:


Meeting Agendas

  • TBD

Chat Logs

  • TBD

Architectural Descriptions/Views used to express this viewpoint

This VAG expresses a client-oriented viewpoint, and hence is concerned only with those Architectural Descriptions/Views that impact on the client. This section identifies:

  1. the general form or representation of ADVs required to express the viewpoint of this VAG
  2. the elements within such ADVs which will be used to express the viewpoint
  3. how these elements within such ADVs map to the concerns of this viewpoint
  4. the traceability to viewpoint concerns required for conformance with the viewpoint.

None decided.

Tools employed by this VAG

  • Normal wiki textual and graphic representations are expected to be sufficient for this VAG.
  • Programmed tools are expected to be developed for interface testing and performance measurement.

External Links

Members (Stakeholders)

Please note that the Multi-Process Client VAG is a non-hierarchical VAG in every respect, without exception. Any tags supplied with names are purely informational. Stakeholder ordering is alphabetical.

Morgaine Dinova 11:00, 7 November 2007 (PDT)
Saijanai Kuhn 11:00, 7 November 2007 (PDT)