LIBOMV-477 Corrects TeleportFailedMessage to use OSDArrays instead of maps even though there doesn't seem to be any reason a viewer would receive multiple responses for the same failed message.

* Moves EventDecoder to MessageUtils utility class
LIBOMV-492 Fixes null reference when message decoder sends a null response

git-svn-id: http://libopenmetaverse.googlecode.com/svn/libopenmetaverse/trunk@2669 52acb1d6-8a22-11de-b505-999d5b087335
This commit is contained in:
Jim Radford
2009-04-27 23:59:49 +00:00
parent 9fa36f6466
commit 8b493316b0
5 changed files with 32 additions and 19 deletions

View File

@@ -31,10 +31,10 @@ using OpenMetaverse.StructuredData;
using OpenMetaverse.Interfaces;
using OpenMetaverse.Messages.Linden;
namespace OpenMetaverse
namespace OpenMetaverse.Messages
{
public partial class Caps
public static partial class MessageUtils
{
/// <summary>
/// Return a decoded capabilities message as a strongly typed object
@@ -77,7 +77,7 @@ namespace OpenMetaverse
case "ViewerStats": message = new ViewerStatsMessage(); break;
case "EventQueueGet": message = new EventQueueGetMessage(); break;
case "CrossedRegion": message = new CrossedRegionMessage(); break;
case "TelportFailed": message = new TeleportFailedMessage(); break;
case "TeleportFailed": message = new TeleportFailedMessage(); break;
// Capabilities TODO: