StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POC# extending SoapExtension -
primarykey
Id
5434975
data
AcceptedAnswerId
5457634
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-03-25T16:02:38.440
FavoriteCount
4
LastActivityDate
2011-03-28T12:29:04.610
LastEditDate
2011-03-28T08:42:21.133
LastEditorUserId
522374
OwnerUserId
522374
ParentId
0
PostTypeId
1
Score
9
ViewCount
2005
LastEditorDisplayName
text
Body
Background: I'm trying to write a simple SoapExtension class to log inbound/outbound Soap messages from an asmx web service. Following <a href="http://msdn.microsoft.com/en-us/library/system.web.services.protocols.soapextension%28VS.85%29.aspx">this article on msdn</a>, I have been able to get things working. However I'd really like to understand why/how it's working rather than just copy & pasting code. The question: What I'm stuggling to grasp specifically is the handling of the IO streams in the example. All other articles I've read on the web handle the streams in an identical way... first getting a reference to the original stream, creating an in memory "working" stream, and then swapping the contents as necessary. First question is, what is meant by "stream chaining" in this context? My understaning of streams is that writing to any stream will automatically write to the 'inner' streams in a pipeline. If that's the case, why is it necessary to manually copy contents from one stream to another? Second question is, in the examples Copy method they're creating a StreamReader and StreamWriter each time, without disposing them - is this not putting extra pressure on the GC? Doesn't seem like something you'd want on a high traffic web service... I tried wrapping both in using statements, but disposing the reader/writer also closed the stream which led to more serious errors. .NET 4 has new Stream.CopyTo(Stream) methods, but what would be a better approach for .NET 3.5?
Tags
<c#><soap><stream><asmx><soap-extension>
Title
C# extending SoapExtension -
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USMattDavey
UserOwnerUserId
1. USMattDavey
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POC# extending SoapExtension -
 UserUserId
 USRup
 VoteTypeVoteTypeId
 VTFavorite
2. VO
 singulars
 PostPostId
 POC# extending SoapExtension -
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POC# extending SoapExtension -
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.