SoapExtension and NetworkStream

[=?Utf-8?B?Q0V2YW5z?=]

My Environment
* Windows XP
* .NET 2.0
* Visual Studio 2005

I have written a SoapExtension in c# on a windows XP machine. The purpose
of this extension is to monitor progress for data being transfered over the
wire. I have a web service that exposes one method. All this method does is
return a byte array of 5 megs. When I call the service I receive all 5 megs,
but my SoapException is not called until all 5 megs have been transfered over
the wire. I am succesfully getting the extension to launch, but by the time
it calls the ChainStream for the deserialization process, the Stream being
passed in is a MemoryStream and not a NetworkStream. I am loading the
SoapExtension through my app.config file with the lines below.

<system.web>
<webServices>
<soapExtensionTypes>
<add
type="WSProgressTest.SoapProgressExtension, WSProgressTest"
priority="0"
group="High" />
</soapExtensionTypes>
</webServices>
</system.web>

From what I understand, a priority of 0 and a group level of "High" should
make my SoapExtension be the first Extention to be called. I would like to
know if there is a way to read from a NetworkStream so I can monitor the rate
at which I am transfering data over the network.

Any insight is appriciated. Please let me know if there is some additional
info that owuld make this question simpler to understand/answer.

Thanks

[=?Utf-8?B?TWFuaXNoIEJhZm5h?=]

Hi,
If you want to moniter the progress of data being sent over wire in web
services then i think tcptrace or fiddler tool is more appropriate:
[1]http://www.fiddlertool.com/fiddler/
[2]http://pocketsoap.com/tcptrace/
--
Hope this helps.
Thanks and Regards.
Manish Bafna.
MCP and MCTS.

"CEvans" wrote:

My Environment
* Windows XP
* .NET 2.0
* Visual Studio 2005

I have written a SoapExtension in c# on a windows XP machine. The purpose
of this extension is to monitor progress for data being transfered over the
wire. I have a web service that exposes one method. All this method does is
return a byte array of 5 megs. When I call the service I receive all 5 megs,
but my SoapException is not called until all 5 megs have been transfered over
the wire. I am succesfully getting the extension to launch, but by the time
it calls the ChainStream for the deserialization process, the Stream being
passed in is a MemoryStream and not a NetworkStream. I am loading the
SoapExtension through my app.config file with the lines below.

<system.web>
<webServices>
<soapExtensionTypes>
<add
type="WSProgressTest.SoapProgressExtension, WSProgressTest"
priority="0"
group="High" />
</soapExtensionTypes>
</webServices>
</system.web>

From what I understand, a priority of 0 and a group level of "High" should
make my SoapExtension be the first Extention to be called. I would like to
know if there is a way to read from a NetworkStream so I can monitor the rate
at which I am transfering data over the network.

Any insight is appriciated. Please let me know if there is some additional
info that owuld make this question simpler to understand/answer.

Thanks

[=?Utf-8?B?Q0V2YW5z?=]

Manish,

Thanks for the response. I went to the wesites you provided and these do
seem like good monitoring tools. Unfortunatly, I am not looking for a
monitoring tool. I am looking at a way to show progress to an end user about
the rate data is being transfered over the network. I am also trying to show
percentage of completion of the data being sent across the network. I have
provided a link below which explains exactly what I am trying to do.
Unfortunately, the stream I am able to intercept with the SoapExtension is
too late in the deserialization process because it is already a memory stream
by that point. I am trying to find out how to intercept the stream earlier
in the deserialization process. I am doing all of my processing in the
BeforeDeserialization stage.

http://www.codeproject.com/useritems...n_Progress.asp
Thanks,
Evans

"Manish Bafna" wrote:

Hi,
If you want to moniter the progress of data being sent over wire in web
services then i think tcptrace or fiddler tool is more appropriate:
[1]http://www.fiddlertool.com/fiddler/
[2]http://pocketsoap.com/tcptrace/
--
Hope this helps.
Thanks and Regards.
Manish Bafna.
MCP and MCTS.

"CEvans" wrote:

My Environment
* Windows XP
* .NET 2.0
* Visual Studio 2005

I have written a SoapExtension in c# on a windows XP machine. The purpose
of this extension is to monitor progress for data being transfered over the
wire. I have a web service that exposes one method. All this method does is
return a byte array of 5 megs. When I call the service I receive all 5 megs,
but my SoapException is not called until all 5 megs have been transfered over
the wire. I am succesfully getting the extension to launch, but by the time
it calls the ChainStream for the deserialization process, the Stream being
passed in is a MemoryStream and not a NetworkStream. I am loading the
SoapExtension through my app.config file with the lines below.

<system.web>
<webServices>
<soapExtensionTypes>
<add
type="WSProgressTest.SoapProgressExtension, WSProgressTest"
priority="0"
group="High" />
</soapExtensionTypes>
</webServices>
</system.web>

From what I understand, a priority of 0 and a group level of "High" should
make my SoapExtension be the first Extention to be called. I would like to
know if there is a way to read from a NetworkStream so I can monitor the rate
at which I am transfering data over the network.

Any insight is appriciated. Please let me know if there is some additional
info that owuld make this question simpler to understand/answer.

Thanks

[=?Utf-8?B?Q0V2YW5z?=]

Any additional insight to my comments below would be appriciated!!!

I figure I would provide at least a partial answer at this point. I am now
able to stream the data as it comes off the wire. What did I change?... Not
too much. I was making an asynchronous WS call through the auto generated
proxy file. I changed the call to be a synchronous call and all of a sudden
things started working. It seems that when an asynch call is made, my
soapextension was not called until after the data was completely transmitted
to the client. When I make a synchronous call, I get access to the
System.Net.Connect stream. I will post again after I figure that out why
their are differences in logical flow for the two calls.