blob: 946261ed15c7dae2cbac689770c4217bb80c7d96 (
plain) (
tree)
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE> [99s-extend] timeout in cowboy loop handler
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20timeout%20in%20cowboy%20loop%20handler&In-Reply-To=%3CCA%2BeMAwZW64xGtVxca35PngCXBJEh8oaQk9TuOPesXf48XUH%3Dqg%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<style type="text/css">
pre {
white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */
}
</style>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000274.html">
<LINK REL="Next" HREF="000276.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[99s-extend] timeout in cowboy loop handler</H1>
<B>akonsu</B>
<A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20timeout%20in%20cowboy%20loop%20handler&In-Reply-To=%3CCA%2BeMAwZW64xGtVxca35PngCXBJEh8oaQk9TuOPesXf48XUH%3Dqg%40mail.gmail.com%3E"
TITLE="[99s-extend] timeout in cowboy loop handler">akonsu at gmail.com
</A><BR>
<I>Wed Oct 16 05:48:42 CEST 2013</I>
<P><UL>
<LI>Previous message: <A HREF="000274.html">[99s-extend] timeout in cowboy loop handler
</A></li>
<LI>Next message: <A HREF="000276.html">[99s-extend] timeout in cowboy loop handler
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#275">[ date ]</a>
<a href="thread.html#275">[ thread ]</a>
<a href="subject.html#275">[ subject ]</a>
<a href="author.html#275">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>1. do you mean that there is no way on the server side to tell if the
client has disconnected?
2. if I use a normal handler, I will still run into the same problem, it
does not matter which handler I use, from the standpoint of deciding
whether the client is still there, right?
I am confused as to how I can implement my streaming and not drop the
connection on each client and yet make sure I do close the connections when
the clients disconnect...
2013/10/15 Loïc Hoguin <<A HREF="https://lists.ninenines.eu/listinfo/extend">essen at ninenines.eu</A>>
><i> Infinite is bad practice, yes. Infinite means some connections will
</I>><i> *never* be closed, eating FDs and memory for nothing.
</I>><i>
</I>><i> I'm not sure why you want to receive messages, you could just use a normal
</I>><i> handler that asks for more data, sends it, ask for more data, sends it, etc.
</I>><i>
</I>><i>
</I>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <<A HREF="http://lists.ninenines.eu/archives/extend/attachments/20131015/bac10460/attachment.html">http://lists.ninenines.eu/archives/extend/attachments/20131015/bac10460/attachment.html</A>>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000274.html">[99s-extend] timeout in cowboy loop handler
</A></li>
<LI>Next message: <A HREF="000276.html">[99s-extend] timeout in cowboy loop handler
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#275">[ date ]</a>
<a href="thread.html#275">[ thread ]</a>
<a href="subject.html#275">[ subject ]</a>
<a href="author.html#275">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend
mailing list</a><br>
</body></html>
|
