-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Hamish Mackenzie
Sent: Thursday, November 28, 2002 11:31 AM
To: Boost mailing list
Subject: RE: [boost] Re: AW: Re: AW: Sockets
[...]
I will take an ostream over writen any day.
Agreed. I will try
On Wed, 2002-11-27 at 19:13, Boris Schäling wrote:
I use std::string as a buffer which grows when needed. This is sufficient
for what I do but may not what others need.
In that case you would be well catered for by.
class buffered_observer : public observer
{
std::stringstream
On Wed, 2002-11-27 at 19:13, Boris Schäling wrote:
I use std::string as a buffer which grows when needed. This is sufficient
for what I do but may not what others need. You are right that there should
be better control of the buffers and/or an on_flush() method to notify the
observer when the
On Tue, 2002-11-26 at 17:12, Boris Schäling wrote:
How does the multiplexor know what to pass to write the second time?
The multiplexor doesn't know but the stream does. The multiplexor calls
stream::write() when the socket descriptor is writable. The stream calls
::write() and sends all
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Hamish Mackenzie
Sent: Wednesday, November 27, 2002 12:53 PM
To: Boost mailing list
Subject: RE: [boost] Re: AW: Re: AW: Sockets
On Tue, 2002-11-26 at 17:12, Boris Schäling wrote:
How does
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Hamish Mackenzie
Sent: Wednesday, November 27, 2002 5:00 PM
To: Boost mailing list
Subject: RE: [boost] Re: AW: Re: AW: Sockets
[...]
My implementation selects on all file descriptors and calls
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Hamish Mackenzie
Sent: Tuesday, November 26, 2002 1:34 AM
To: Boost mailing list
Subject: RE: [boost] Re: AW: Re: AW: Sockets
On Mon, 2002-11-25 at 23:56, Boris Schäling wrote:
This looks like
From: Boris Schäling [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 27 November 2002 3:12 AM
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Hamish Mackenzie
How does the multiplexor know what to pass to write the second time?
The multiplexor doesn't know but the stream
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Hamish Mackenzie
Sent: Monday, November 25, 2002 2:43 AM
To: Boost mailing list
Subject: RE: [boost] Re: AW: Re: AW: Sockets
[...]
I added
http://www.crystalclearsoftware.com/cgi-bin
On Mon, 2002-11-25 at 20:57, Boris Schäling wrote:
Looks good but am I correct in thinking it uses blocking writes to the
socket? (no on_write). This is ok for some applications but would not
work for sending large files or streaming live content.
The library uses non-blocking write. If
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Hamish Mackenzie
Sent: Monday, November 25, 2002 11:53 PM
To: Boost mailing list
Subject: RE: [boost] Re: AW: Re: AW: Sockets
On Mon, 2002-11-25 at 20:57, Boris Schäling wrote:
Looks good but am
I will try to set up another page at Boost Wiki to explain in
detail what I mean by multiplexing library.
This is interesting, but the only intersection with sockets seems
to be at the socket_stream level (which appears to be an undefined
concept in the current wiki pages, but is in the
On Sun, 2002-11-24 at 21:23, Jeff Garland wrote:
Is there a reason why we can't define a simple socket library first
as a lower layer without the complications of multiplexing and
threading and then add those on top?
That seems reasonable, since due to the great differences between the
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Hugo Duncan
Sent: Sunday, November 24, 2002 12:11 AM
To: [EMAIL PROTECTED]
Subject: [boost] Re: AW: Re: AW: Sockets
Boris,
On Sat, 23 Nov 2002 21:35:58 +0100, Boris Schäling
[EMAIL PROTECTED]
14 matches
Mail list logo
