+2005-05-31 Lluis Sanchez Gual <lluis@novell.com>
+
+ * ReturnMessage.cs: Added some null checks.
+ * MethodReturnMessageWrapper.cs: Added some null checks. Fixed
+ incorrect cast in the constructor.
+
+2005-05-20 Sebastien Pouliot <sebastien@ximian.com>
+
+ * AsyncResult.cs: Added new fields (required for stack propagation) to
+ match runtime structure.
+
+2005-05-09 Lluis Sanchez Gual <lluis@novell.com>
+
+ * MethodCall.cs: Fix warning.
+
+2004-10-26 Lluis Sanchez Gual <lluis@novell.com>
+
+ * CallContext.cs: In CreateLogicalCallContext, added parameter which
+ specifies if an empty LogicalCallContext needs to be created if there are
+ no context values.
+
+2004-09-27 Lluis Sanchez Gual <lluis@novell.com>
+
+ * MethodCallMessageWrapper.cs: The wrapper has to modify the wrapped
+ message. MS does it.
+ * ReturnMessage.cs: Use TypeName instead of _typeName since now name is
+ lazely constructed.
+
+2004-09-22 Lluis Sanchez Gual <lluis@novell.com>
+
+ * ConstructionCall.cs: Added a Proxy property (which is the proxy that
+ will reference the object being created).
+ * StackBuilderSink.cs: Take into account the forceInternalExecute
+ parameter.
+
+2004-09-11 Ben Maurer <bmaurer@users.sourceforge.net>
+
+ * CallContext.cs: Use [ThreadStatic], it is much faster than the
+ Thread.[Get/Set]Data functions
+
+2004-09-11 Ben Maurer <bmaurer@users.sourceforge.net>
+
+ * CADMessages.cs: get rid of method / type name, it is not needed
+ * MethodCall.cs: lazily init method / type name.
+ * ReturnMessage.cs: lazily init method / type name, sig.
+
+2004-09-11 Ben Maurer <bmaurer@users.sourceforge.net>
+
+ * CADMessages.cs, MethodCall.cs: When doing an x-appdomain
+ call, store the method in a RuntimeMethodHandle. This allows
+ us to avoid the expensive lookup operations that must be done
+ to resolve the method. This makes xsp go from 250 r/s to 450 r/s
+ for me.
+
+2004-09-05 Ben Maurer <bmaurer@users.sourceforge.net>
+
+ * MethodCall.cs, CADMessages.cs: String.Copy (x) is the same
+ thing as new string (x.ToCharArray ()), however it involves
+ half the memory allocation
+
+2004-07-22 Lluis Sanchez Gual <lluis@novell.com>
+
+ * MethodCall.cs: Use RemotingServices.GetMethodBaseFromName to get the
+ MethodBase from the method name. This fixes bug #61774.
+
+2004-06-18 Sebastien Pouliot <sebastien@ximian.com>
+
+ * ReturnMessage.cs: Added IMessage interface to class definition.
+
+2004-06-17 Gert Driesen <drieseng@users.sourceforge.net>
+
+ * ReturnMessage.cs: remove serializable attribute to match MS.NET
+
+2004-05-11 Lluis Sanchez Gual <lluis@ximian.com>
+
+ * MethodResponse.cs: Only get the MethodBase from type and method name when
+ requested.
+
+2004-05-11 Lluis Sanchez Gual <lluis@ximian.com>
+
+ * MethodResponse.cs: In the serialization constructor, initialize MethodBase
+ using the method name and type name.
+
+2004-05-03 Lluis Sanchez Gual <lluis@ximian.com>
+
+ * MethodResponse.cs, ReturnMessage.cs: More null checks.
+
+2004-04-30 Lluis Sanchez Gual <lluis@ximian.com>
+
+ * MethodResponse.cs, ReturnMessage.cs: Added null checks.
+
+2004-04-29 Raja R Harinath <rharinath@novell.com>
+
+ * MethodResponse.cs (MethodResponse.OutArgCount)
+ (MethodResponse.GetOutArg): Make reference to _args null-safe.
+
+2004-04-28 Lluis Sanchez Gual <lluis@ximian.com>
+
+ * CADMessages.cs: Revert last change. It was ok.
+ * MethodResponse.cs, ReturnMessage.cs: Handle output parameters in a
+ different way. The message is constructed from an array that has all
+ parameters, including input parameters (which will be set to null).
+ The Args property returns all arguments. OutArgs returns only the
+ output arguments, which are taken from the provided args list.
+
+2004-04-26 Lluis Sanchez Gual <lluis@ximian.com>
+
+ * CADMessages.cs: Marshal the correct return args for the return message.
+
+2004-02-18 Gonzalo Paniagua Javier <gonzalo@ximian.com>
+
+ * AsyncResult.cs:
+ (AsyncWaitHandle): create the handle if not done yet.
+
+2004-01-19 Lluis Sanchez Gual <lluis@ximian.com>
+
+ * AsyncResult.cs: Added async_callback field and fixed the callback call.
+ I thought that async_delegate was the callback, but it is not, it is the
+ delegate upon which the async call was invoked. This fixes bug #53020.
+ * StackBuilderSink.cs: If the target object is a proxy, make the call
+ using the Invoke method of the real proxy.
+
+2003-12-23 Lluis Sanchez Gual <lluis@ximian.com>
+
+ * ConstructionResponse.cs: Added constructor for exception response.
+
+2003-12-22 Lluis Sanchez Gual <lluis@ximian.com>
+
+ * MethodCall.cs: Do not try to resolve the method in the serialization
+ constructor, since the type array may not be yet completely deserialized.
+ This fixes bug #52426.
+
+2003-12-10 Lluis Sanchez Gual <lluis@ximian.com>
+
+ * AsyncResult.cs: Call delegate on async call completion.
+ * CADMessages.cs: Removed TODO.
+
+2003-11-28 Dick Porter <dick@ximian.com>
+
+ * MethodCall.cs: Use the char form of IndexOf, so that the
+ comparison is done with the Invariant culture.
+
+2003-11-26 Lluis Sanchez Gual <lluis@ximian.com>
+
+ * MethodCall.cs, MethodResponse.cs, ReturnMessage.cs: Implemented
+ HasVarArgs property.
+
+2003-11-25 Lluis Sanchez Gual <lluis@ximian.com>
+
+ * AsyncResult.cs, CallContext.cs: Added private constructor.
+ * ReturnMessage.cs: Added parameter array length check.
+
+2003-11-18 Lluis Sanchez Gual <lluis@ximian.com>
+
+ * ArgInfo.cs, ClientContextTerminatorSink.cs, ErrorMessage.cs, MethodCall.cs,
+ MethodResponse.cs, MonoMethodMessage.cs, ServerContextTerminatorSink.cs,
+ StackBuilderSink.cs: Fixed class visibility.
+ * CADMessages.cs: Added null reference check in SaveLogicalCallContext.
+ * ISerializationRootObject.cs: Added.
+
2003-11-17 Lluis Sanchez Gual <lluis@ximian.com>
* StackBuilderSink.cs: Implemented AsyncProcessMessage().