Comments on: Flash Socket Class Does Not Wait For Flush

By: Steven Sacks

Steven Sacks — Thu, 08 Apr 2010 21:07:11 +0000

That is incorrect. You haven't tested this. If you had, you would know that what you just said is wrong.

I am on Windows and when I write to the Socket, the server immediately receives it. Same thing happens on Mac and Linux. There is no platform inconsistency.

I'm surprised that Adobe still hasn't updated the documentation.

By: Joe Ward

Joe Ward — Thu, 08 Apr 2010 21:02:55 +0000

As to the flush() behavior, on Mac and Linux, flush() is called implicitly between execution frames. So if you wrote two bytes in different write calls in the same function, for example, those two bytes are sent together. If the writes were separated by an async event, then they would be sent separately.

However, on Windows, data is never sent unless you call flush(). The platform inconsistency is a bug, but the docs were essentially correct (just incomplete).

By: Steven Sacks

Steven Sacks — Thu, 11 Mar 2010 21:18:15 +0000

There is no flushing of a socket. The moment you say socket.writeWhatever, the bytes are sent to the server immediately.

By: 62316e

62316e — Thu, 11 Mar 2010 15:49:31 +0000

So, how to flush socket?

By: Steven Sacks

Steven Sacks — Wed, 24 Feb 2010 03:25:20 +0000

It's been almost 3 months and the documentation remains unchanged. Will you be updating this anytime soon?

By: maliboo

maliboo — Wed, 09 Dec 2009 13:10:59 +0000

As Steven said there are huge problems with getting sending progress with Socket class. So don;t forget to vote on this bug@Adobe JIRA:
http://bugs.adobe.com/jira/browse/FP-6

By: Steven Sacks

Steven Sacks — Wed, 09 Dec 2009 00:15:31 +0000

Thanks! Now how about returning progress, or being able to see how many bytes remain on the socket so I can tell if the socket is blocked, etc.

By: Jody Bleyle

Jody Bleyle — Wed, 09 Dec 2009 00:05:24 +0000

Nice catch, Steven, thank you. I'm updating the documentation source now and we'll push the changes live as soon as we can.

Jody Bleyle
Sr. Technical Writer
Adobe Systems, Inc.

By: Steven Sacks

Steven Sacks — Tue, 08 Dec 2009 21:15:05 +0000

Ok, so it's confirmed (from you and elsewhere) that Socket sends the data the moment you write anything to it.

The documentation is wrong throughout (every write function says it doesn't send until you call flush, and flush says it sends the data, but, in fact, does nothing because the data is already sent instantly).

By: Gardner

Gardner — Tue, 08 Dec 2009 21:10:13 +0000

Unfortunately sockets are kinda like this at the system level as well. Flushing just ensures that there is no queued data but once you chuck the data into send() it gets sent whenever the tcp stack gets around to it. Check out http://msdn.microsoft.com/en-us/library/ms740149%28VS.85%29.aspx Specifically: "If no error occurs, send returns the total number of bytes sent, which can be less than the number requested to be sent in the len parameter." At least the winsock api tell you how many bytes you've sent…