StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20526311
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-11T17:46:34.843
FavoriteCount
0
LastActivityDate
2013-12-11T17:46:34.843
LastEditDate
LastEditorUserId
0
OwnerUserId
561545
ParentId
16502068
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I think I had a similar issue. I was sending JSON strings using the Socket class, and suddenly JSON.NET would throw an exception. I inspected the string, and I saw that 2 JSON (root) objects were being processed. I then threw together a minimal example, and found that the socket will stash* any unread data (unread = no .Receive has been called yet, and .Receive will clear the stash). *stash: I am not sure if this is the correct term. It made sense to me. Here is my test. If you want to run it, create a new test class and install XUnit. <pre><code>/// <summary> /// Testing Net Sockets.. /// </summary> /// <author>Jeff Hansen</author> public class SocketTests { /// <summary> /// The local endpoint for the server. There's no place like 127.0.0.1 /// </summary> private IPEndPoint endpoint = new IPEndPoint(IPAddress.Parse("127.0.0.1"), 1337); /// <summary> /// Tests that a call to .Receive will return all unread data. /// </summary> /// <author>Jeff Hansen</author> [Fact] public void ReceiveWillReadAllUnreadData() { // We expect to receive double data. const string expected = "HELLOHELLO"; const string dataToSend = "HELLO"; // Start the server in a background task. // We do this because the receive call is blocking. var bgTask = Task.Factory.StartNew(() => { var server = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp); try { // Bind to the endpoint and start listening. server.Bind(endpoint); server.Listen(10); // 10 is max allowed connections in queue (I think) // Client connected, receive data var connectingClient = server.Accept(); // So low-level we even get to allocate room for the data buffer manually. var buf = new byte[1024]; // Hangs until data flows. var sz = connectingClient.Receive(buf); // This is the size of the data we just received. var data = Encoding.ASCII.GetString(buf, 0, sz); // We use the size to only grab what we need from the buffer. Console.WriteLine("Data received: {0}", data); // This is going to pass because we sent the data twice, // and the call to Receive would not be able to complete in time // for it to clear before more data becomes available. Assert.Equal(expected, data); /* * BAM! Theory proven. We seriously had issues * because we didn't understand how it worked. This is why you usually end * your transmission with a newline. */ Console.WriteLine("Server closing"); server.Close(); } catch (Exception e) { // Make sure we close the server. server.Close(); throw; } }); // Create a client socket and connect it to the server. // The server thread should have started it up by now. var client = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp); client.Connect(endpoint); // Get the bytes of our string var buffer = Encoding.ASCII.GetBytes(dataToSend); // Send it out twice. This happens faster than the server will process it, // so the data is stacking up. You would THINK that .Receive would // simply return the first data sent to it, and the next time .Receive is called // return the next. But that's not how it works, apparently. client.Send(buffer); client.Send(buffer); // Wait for the server to finish whatever it's doing. try { // We give it 3000ms to complete. bgTask.Wait(); } catch (AggregateException ag) { // Throw any esceptions that were thrown in the background thread. ag.Handle(ex => { throw ex; }); } // Close the client socket. client.Close(); } } </code></pre> We solved it by delimiting our data with a newline. Fun fact: I was messing with TcpClient, and found that if I did not write a newline to the stream, it would not send anything - it would just hang there. Might have been a localized issue though. Anyone care to elaborate on that?
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC# socket receiving thread
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJeff
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.