This page contains new concept of verse resend mechanism, handshake, teardown etc. Keep in mind, that following text is work in progress. Copyright 2008-2013 Jiří Hnídek.

The Verse protocol uses client-server architecture. The server holds data and distributes changes of data between connected clients. For example, when a client sends a message containing new position of the object to the server, then server would retransmit this information to other clients interested in this object. From this point of view the Verse protocol looks like a network protocol used in gaming applications, but the Verse protocol allows much more. Applications can share not only the object transformations but also geometry and topology of objects, materials, textures, UV coordinates etc. On the other side, the Verse protocol does not allow to use multicast connections because each client requires a different set of data. Each client can support a different types of data (for example: only geometry and object transformations) as well as each client is usually subscribed to different nodes.

The specification of Verse protocol is split into several parts

• Data Types
• Transport Layer
• Security
• Structure of Packet and Message
• User Authentication
• Negotiation
• Handshake of Datagrame Connection
• Teardown of Datagrame Connection
• Resend Mechanism
• Congestion Control
• Flow Control

Proposal of WebSocket and TCP variant

• TCP Variant
• Websocket Variant

Following sections contains specification of commands

• Node Commands
• Tag Group Commands
• Tag Commands
• Layer Commands

Structure of shared data

• Data Model
• Versioning