OpenSim 0.6 IClientAPI
From OpenSimulator
(Difference between revisions)
(→Instant Message) |
(→Porting Guide) |
||
| Line 5: | Line 5: | ||
* Dropping fromAgentSession from SendInstantMessage (both overloaded versions) | * Dropping fromAgentSession from SendInstantMessage (both overloaded versions) | ||
** Rationale: Session ID is both linden specific, and something that shouldnt be transmitted to users anyway ('''security'''). | ** Rationale: Session ID is both linden specific, and something that shouldnt be transmitted to users anyway ('''security'''). | ||
| − | ** IClientAPI changes: Insert this parameter into your packets manually, LLClientView.cs contains a reference to sessionID already. | + | ** IClientAPI changes: Insert this parameter into your packets manually if you need it, LLClientView.cs contains a reference to sessionID already. Be advised that this represents a security risk (giving the users one of the two shared secrets). |
* Dropping imSessionID from SendInstantMessage (both overloaded versions) | * Dropping imSessionID from SendInstantMessage (both overloaded versions) | ||
** Rationale: IM Session ID's are unique to SL and we just multiplex the two users ID's to form this so it's static anyway. | ** Rationale: IM Session ID's are unique to SL and we just multiplex the two users ID's to form this so it's static anyway. | ||
** IClientAPI changes: Multiplex the ID inside your own implementations vs relying on the module to do it for you. | ** IClientAPI changes: Multiplex the ID inside your own implementations vs relying on the module to do it for you. | ||
| + | ==Bluebox== | ||
| + | * Dropping sessionID from SendBlueBoxMessage | ||
| + | ** Rationale: Session ID is both linden specific, and something that shouldnt be transmitted to users anyway ('''security'''). | ||
| + | ** IClientAPI changes: Insert this parameter into your packets manually if you need it, LLClientView.cs contains a reference to sessionID already. Be advised that this represents a security risk (giving the users one of the two shared secrets). | ||
Revision as of 10:19, 8 November 2008
|
|
This article or section contains incomplete information. Please help us by completing the content on this page. |
This page is under construction.
Porting Guide
Instant Message
- Dropping fromAgentSession from SendInstantMessage (both overloaded versions)
- Rationale: Session ID is both linden specific, and something that shouldnt be transmitted to users anyway (security).
- IClientAPI changes: Insert this parameter into your packets manually if you need it, LLClientView.cs contains a reference to sessionID already. Be advised that this represents a security risk (giving the users one of the two shared secrets).
- Dropping imSessionID from SendInstantMessage (both overloaded versions)
- Rationale: IM Session ID's are unique to SL and we just multiplex the two users ID's to form this so it's static anyway.
- IClientAPI changes: Multiplex the ID inside your own implementations vs relying on the module to do it for you.
Bluebox
- Dropping sessionID from SendBlueBoxMessage
- Rationale: Session ID is both linden specific, and something that shouldnt be transmitted to users anyway (security).
- IClientAPI changes: Insert this parameter into your packets manually if you need it, LLClientView.cs contains a reference to sessionID already. Be advised that this represents a security risk (giving the users one of the two shared secrets).
