[Mono-devel-list] HttpWorkerRequest

Gonzalo Paniagua Javier gonzalo at ximian.com
Tue Dec 14 23:08:26 EST 2004


[...]

>tempBuff will always be null until GetPreloadedEntityBody() is
>implemented in HttpWorkerRequest   >Yes I could check for null and that
would get rid of the error but it >would not make the code functional.
In fact if I did check for null and >found null, my inclination would be
to throw an exception so why not >windows .NET and should work under
mono at some point if I understand >the goals of mono correctly.   >My
original question is only to inquire when the methods of
>HttpWorkerRequest will be implemented.  You said the methods are
>implemented in XSP in classes derived from HttpWorkerRequest, but my
>code refers directly to HttpWorkerRequest not to any derived class.
>Will the methods ever be implemented directly on HttpWorkerRequest in
>mono? 
I think you're misundertanding. That method is already implemented in
HttpWorkerRequest.cs. It just returns null. That's the implementation.
You can easilly test that is the behavior that MS NET has in that method
of HttpWorkerRequest class. How? Derive your own class from
HttpWorkerRequest and call GetPreloadedEntityBody(). You'll always get
null.

Moreover, you have HasEntityBody() and IsEntireEntityBodyIsPreloaded()
to know in advance if GetPreloadedEntityBody() can be null.

-Gonzalo





More information about the Mono-devel-list mailing list