Talk:Varregion/Protocol - Revision history

Manni at 08:23, 20 May 2023

2023-05-20T08:23:08Z

Ubit at 20:41, 16 May 2023

2023-05-16T20:41:35Z

Ubit at 20:40, 16 May 2023

2023-05-16T20:40:09Z

Ubit at 20:39, 16 May 2023

2023-05-16T20:39:30Z

Ubit at 20:39, 16 May 2023

2023-05-16T20:39:20Z

Animats: Aurora-form varregions seem to be obsolete.

2023-05-14T20:17:15Z

Aurora-form varregions seem to be obsolete.

New page

Noted that the old Aurora UDP messages for varregion size are now obsolete. Unclear how it's done now. Ubit says this is now done via a capability. Name and format of that capability are unknown.--[[User:Animats|Animats]] ([[User talk:Animats|talk]]) 13:17, 14 May 2023 (PDT)

@@ Line 1: / Line 1: @@
 Noted that the old Aurora UDP messages for varregion size are now obsolete. Unclear how it's done now. Ubit says this is now done via a capability. Name and format of that capability are unknown.--[[User:Animats|Animats]] ([[User talk:Animats|talk]]) 13:17, 14 May 2023 (PDT)
 They are encapsulated in a Event capability message, with same name. The fields are same (with some extensions for var regions), with same names as on lludp message template file, and are encoded in LLSD, typically LLSDxml.
 SL viewers and derivatives, convert the serialized data of LLUDP or Event, to a internal format (LLSD) and may use shared processing code (Ubit May 15 2023)

← Older revision		Revision as of 20:41, 16 May 2023
Line 2:		Line 2:

	They are encapsulated in a Event capability message, with same name. The fields are same (with some extensions for var regions), with same names as on lludp message template file, and are encoded in LLSD, typically LLSDxml.		They are encapsulated in a Event capability message, with same name. The fields are same (with some extensions for var regions), with same names as on lludp message template file, and are encoded in LLSD, typically LLSDxml.
−	SL viewers and derivatives, convert the serialized data to a internal format (LLSD) and may use shared processing code (Ubit May 15 2023)	+	SL viewers and derivatives, convert the serialized data of LLUDP or Event, to a internal format (LLSD) and may use shared processing code (Ubit May 15 2023)

← Older revision		Revision as of 20:40, 16 May 2023
Line 2:		Line 2:

	They are encapsulated in a Event capability message, with same name. The fields are same (with some extensions for var regions), with same names as on lludp message template file, and are encoded in LLSD, typically LLSDxml.		They are encapsulated in a Event capability message, with same name. The fields are same (with some extensions for var regions), with same names as on lludp message template file, and are encoded in LLSD, typically LLSDxml.
−	SL viewers and derivatives, convert the serialized data to a internal format (LLSD) and may use shared processing code	+	SL viewers and derivatives, convert the serialized data to a internal format (LLSD) and may use shared processing code (Ubit May 15 2023)

@@ Line 1: / Line 1: @@
 Noted that the old Aurora UDP messages for varregion size are now obsolete. Unclear how it's done now. Ubit says this is now done via a capability. Name and format of that capability are unknown.--[[User:Animats|Animats]] ([[User talk:Animats|talk]]) 13:17, 14 May 2023 (PDT)
 They are encapsulated in a Event capability message, with same name. The fields are same (with some extensions for var regions), with same names as on lludp message template file, and are encoded in LLSD, typically LLSDxml.
 SL viewers and derivatives, convert the serialized data to a internal format (LLSD) and may use shared processing code

← Older revision		Revision as of 20:39, 16 May 2023
Line 1:		Line 1:
	Noted that the old Aurora UDP messages for varregion size are now obsolete. Unclear how it's done now. Ubit says this is now done via a capability. Name and format of that capability are unknown.--[[User:Animats\|Animats]] ([[User talk:Animats\|talk]]) 13:17, 14 May 2023 (PDT)		Noted that the old Aurora UDP messages for varregion size are now obsolete. Unclear how it's done now. Ubit says this is now done via a capability. Name and format of that capability are unknown.--[[User:Animats\|Animats]] ([[User talk:Animats\|talk]]) 13:17, 14 May 2023 (PDT)
		+	They are encapsulated in a Event capability message, with same name. The fields are same (with some extensions for var regions), with same names as on lludp message template file, and are encoded in LLSD, typically LLSDxml.
		+	SL viewers and derivatives, convert the serialized data to a internal format (LLSD) and may use shared processing code