Click here to Skip to main content
15,910,130 members
Home / Discussions / C#
   

C#

 
QuestionAdvices for my learning path Pin
coco2437-Jul-23 21:10
coco2437-Jul-23 21:10 
AnswerRe: Advices for my learning path Pin
OriginalGriff7-Jul-23 21:19
mveOriginalGriff7-Jul-23 21:19 
AnswerRe: Advices for my learning path Pin
Richard Andrew x648-Jul-23 3:26
professionalRichard Andrew x648-Jul-23 3:26 
GeneralRe: Advices for my learning path Pin
coco2439-Jul-23 9:07
coco2439-Jul-23 9:07 
GeneralRe: Advices for my learning path Pin
jschell10-Jul-23 3:50
jschell10-Jul-23 3:50 
AnswerRe: Advices for my learning path Pin
BillWoodruff9-Jul-23 15:06
professionalBillWoodruff9-Jul-23 15:06 
GeneralRe: Advices for my learning path Pin
coco24310-Jul-23 18:34
coco24310-Jul-23 18:34 
GeneralRe: Advices for my learning path Pin
BillWoodruff10-Jul-23 18:58
professionalBillWoodruff10-Jul-23 18:58 
GeneralRe: Advices for my learning path Pin
Richard MacCutchan10-Jul-23 21:55
mveRichard MacCutchan10-Jul-23 21:55 
AnswerRe: Advices for my learning path Pin
Gerry Schmitz18-Jul-23 6:03
mveGerry Schmitz18-Jul-23 6:03 
GeneralRe: Advices for my learning path Pin
coco24319-Jul-23 18:36
coco24319-Jul-23 18:36 
QuestionGoogle People API Error Pin
Kevin Marois6-Jul-23 10:54
professionalKevin Marois6-Jul-23 10:54 
AnswerRe: Google People API Error Pin
OriginalGriff6-Jul-23 18:30
mveOriginalGriff6-Jul-23 18:30 
GeneralRe: Google People API Error Pin
Kevin Marois7-Jul-23 6:26
professionalKevin Marois7-Jul-23 6:26 
GeneralRe: Google People API Error Pin
OriginalGriff7-Jul-23 6:45
mveOriginalGriff7-Jul-23 6:45 
Questionwhy the data been sent out after socket.close(), not socket.send(). Pin
viming4-Jul-23 16:06
viming4-Jul-23 16:06 
AnswerRe: why the data been sent out after socket.close(), not socket.send(). Pin
OriginalGriff4-Jul-23 18:19
mveOriginalGriff4-Jul-23 18:19 
GeneralRe: why the data been sent out after socket.close(), not socket.send(). Pin
viming4-Jul-23 21:05
viming4-Jul-23 21:05 
GeneralRe: why the data been sent out after socket.close(), not socket.send(). Pin
OriginalGriff4-Jul-23 21:14
mveOriginalGriff4-Jul-23 21:14 
AnswerRe: why the data been sent out after socket.close(), not socket.send(). Pin
jschell5-Jul-23 5:26
jschell5-Jul-23 5:26 
viming wrote:
should be sent out after sockct.send


That is what I thought a long time ago.

But a 'socket' is just a implementation of the protocol 'TCP' (built on 'IP') and that is how it works. Actually a socket just connects to the OS driver that implements that.

I found that in practice it doesn't matter. It gets sent quickly enough.

Other thing you might keep in mind is that only writes, not reads, require that a socket is actually communicating. Thus if you unplug your computer from the network while a computer at the other end it waiting ('read') for you to send something it will stay that way forever (while application is running.)

There are several ways that can happen usually involving infrastructure failures. But just a simple as someone accidently unplugging a network cable (plugging the cable back in does not fix that.)

That is why reads must set a timeout. Every socket implementation I have used always sets that to infinite by default.
QuestionProblem with string array? Pin
Member 140558794-Jul-23 6:28
Member 140558794-Jul-23 6:28 
AnswerRe: Problem with string array? Pin
Dave Kreskowiak4-Jul-23 7:06
mveDave Kreskowiak4-Jul-23 7:06 
AnswerRe: Problem with string array? Pin
OriginalGriff4-Jul-23 18:21
mveOriginalGriff4-Jul-23 18:21 
GeneralRe: Problem with string array? Pin
jschell5-Jul-23 5:28
jschell5-Jul-23 5:28 
QuestionPredicateBuilder Question Pin
Kevin Marois30-Jun-23 8:54
professionalKevin Marois30-Jun-23 8:54 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.