diff options
| author | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
| commit | 0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch) | |
| tree | 2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2001-February/000263.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to 'pipermail/nel/2001-February/000263.html')
| -rw-r--r-- | pipermail/nel/2001-February/000263.html | 102 |
1 files changed, 102 insertions, 0 deletions
diff --git a/pipermail/nel/2001-February/000263.html b/pipermail/nel/2001-February/000263.html new file mode 100644 index 00000000..863c4810 --- /dev/null +++ b/pipermail/nel/2001-February/000263.html @@ -0,0 +1,102 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] NeL Network Engine</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:cblt%40cblt.org"> + <LINK REL="Previous" HREF="000308.html"> + <LINK REL="Next" HREF="000260.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] NeL Network Engine</H1> + <B>Nicolas Hognon</B> + <A HREF="mailto:cblt%40cblt.org" + TITLE="[Nel] NeL Network Engine">cblt@cblt.org</A><BR> + <I>Thu, 22 Feb 2001 23:12:39 +0100</I> + <P><UL> + <LI> Previous message: <A HREF="000308.html">[Nel] NeL Network Engine</A></li> + <LI> Next message: <A HREF="000260.html">[Nel] Memory error</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#263">[ date ]</a> + <a href="thread.html#263">[ thread ]</a> + <a href="subject.html#263">[ subject ]</a> + <a href="author.html#263">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>><i> (A) If no buffer space is available within the transport system to hold +</I>><i> the data to be transmitted, the actual sending will block. Has anybody +</I>><i> come across this case ? When does this happen in practice ? +</I> +i'm not sure that i understand this part of your mail and i hope you'll +understand my answer because i'm not sure my english enough fluent :)) + +you're asking want happened if you call send or write on a socket +and there is not enough space in the tcp stack / transport layer buffer. +it depends you've got blocking or non blocking socket. +if it's a blocking socket you're thread will be blocked +until you're data can be send by the tcp stack. +if you're socket is in non blocking mode send/write +will return you an error an errno will be EWOULDBLOCK +or WSAEWOULDBLOCK under winsock. + +but i'm not sure it's the answer to your question +because it is not a very huge problem. +i make the same mistake because when you make +some little test it's more common that receive failed +with a wouldblock than send. when i began +writting our network api (for the company i work) +i made this mistake. but when i made +some test with huge network messages and a poor modem +i encounter tihs problem. + +i hope this help you +but can you answer me that i know if i understand +your problem :)) + + +-- +Nicolas Hognon +home : <A HREF="mailto:cblt@cblt.org">cblt@cblt.org</A> / www.cblt.org +work : <A HREF="mailto:nicolash@virtools.com">nicolash@virtools.com</A> / www.virtools.com +#ICQ : 36044443 + +Enjoy the silence +(DM) + + +</pre> + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000308.html">[Nel] NeL Network Engine</A></li> + <LI> Next message: <A HREF="000260.html">[Nel] Memory error</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#263">[ date ]</a> + <a href="thread.html#263">[ thread ]</a> + <a href="subject.html#263">[ subject ]</a> + <a href="author.html#263">[ author ]</a> + </LI> + </UL> +</body></html> |