On 16/04/2012 20:58, Stefan Schwarzer wrote:
Hello,
Here's a summary of the messages which reached me in this
newsgroup and by e-mail. They are ordered by the time they
reached me at.
(According to the headers, each of the answers went to
either comp.lang.python or python-list@python.org . I
th
Hello,
Here's a summary of the messages which reached me in this
newsgroup and by e-mail. They are ordered by the time they
reached me at.
(According to the headers, each of the answers went to
either comp.lang.python or python-list@python.org . I
thought there was some kind of gateway, but in my
Stefan Schwarzer wrote:
Hello,
I wrote a `Connection` class that can be found at [1]. A
`Connection` object has a method `put_bytes(data)` which
returns a "future" [2]. The data will be sent asynchronously
by a thread attached to the connection object.
The future object returned by `put_bytes`
On 15Apr2012 00:22, Stefan Schwarzer wrote:
| I wrote a `Connection` class that can be found at [1]. A
| `Connection` object has a method `put_bytes(data)` which
| returns a "future" [2]. The data will be sent asynchronously
| by a thread attached to the connection object.
[...]
| put_result =
Stefan Schwarzer wrote:
> Hello,
>
> I wrote a `Connection` class that can be found at [1]. A
> `Connection` object has a method `put_bytes(data)` which
> returns a "future" [2]. The data will be sent asynchronously
> by a thread attached to the connection object.
>
> The future object returned
On 04/14/2012 04:22 PM, Stefan Schwarzer wrote:
> However, I'm not comfortable with the combination of the
> names of the future and its method. After all, not the
> `put_result` was sent, but the data that was the argument in
> the `put_bytes` call. Maybe `data_was_sent` is better than
> `was_sent
Hi Stefan,
What do you think would be a "natural" way to name the
> future returned by `put_bytes` and possibly the `was_sent`
> method attached to it? Can you even come up with nice naming
> rules for futures and their methods? :-)
>
I think the intended way to get notified when a future is done
On Sun, Apr 15, 2012 at 8:22 AM, Stefan Schwarzer
wrote:
> The future object returned by `put_bytes` has a `was_sent`
> method which will return `True` once the sender thread has
> actually sent the data via a socket call.
Dunno if this throws a spanner in your works, but does the future
object e
Hello,
I wrote a `Connection` class that can be found at [1]. A
`Connection` object has a method `put_bytes(data)` which
returns a "future" [2]. The data will be sent asynchronously
by a thread attached to the connection object.
The future object returned by `put_bytes` has a `was_sent`
method wh
