StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13157030
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-31T11:37:48.420
FavoriteCount
0
LastActivityDate
2012-10-31T11:50:51.813
LastEditDate
2012-10-31T11:50:51.813
LastEditorUserId
213550
OwnerUserId
213550
ParentId
7765540
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
As @Igby Largeman pointed out, you can use your <code>IIS7</code> to enable the compression on the server, but this is not enough. The main idea is to set the headers on the client side and server side: Client: <pre><code>Accept-Encoding = "gzip, deflate"; </code></pre> You can achieve this by code: <pre><code>var request = HttpWebRequest.Create("http://foofoo"); request.Headers["Accept"] = "application/json"; request.Headers["Accept-Encoding"] = "gzip, deflate"; </code></pre> or <pre><code>var request = HttpWebRequest.Create("http://foofoo"); request.AutomaticDecompression = DecompressionMethods.GZip | DecompressionMethods.Deflate; </code></pre> If you use some WCF client, and not the <code>HttpWebRequest</code>, you should use custom inspector and dispatcher, like in <a href="http://bloggingabout.net/blogs/ramon/archive/2008/11/06/wcf-and-http-gzip-deflate-compression-and-silverlight.aspx" rel="nofollow">this article</a>: <blockquote> So I used a message inspector implementing <code>IClientMessageInspector</code> and <code>IDispatchMessageInspector</code> to automatically set the <code>AcceptEncoding</code> and <code>ContentEncoding</code> http headers. This was working perfectly but I could not achieve to decompress the response on the server by first detecting the <code>ContentEncoding</code> header thus I used the work around to first try to decompress it and if it fails just try to process the request as normal. I also did this in the client pipeline and this also works. </blockquote> Server: <pre><code>// This is the nearly same thing after all Content-Encoding = "gzip" OR Content-Encoding = "deflate" </code></pre> To do this on the Server side, you should enable httpCompression in the IIS. I think you should check the <a href="http://www.hanselman.com/blog/EnablingDynamicCompressionGzipDeflateForWCFDataFeedsODataAndOtherCustomServicesInIIS7.aspx" rel="nofollow">original article</a> to get this work
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWebservice Client and Compression
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USVMAtm
UserOwnerUserId
1. USVMAtm
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.