Bug summary
__
Summary for 2013-11-17 through 2013-11-24
Opened Closed Total Change
Enhancements: 7 3 1142 +4
Defects: 4 2705 +2
Tasks: 0 0 9
On 23/11/13 12:03, Maciej Wasilak wrote:
3. There is a problem with txThings IPv6 server, because in most
operating systems source address of datagram is determined in round
robin fashion. It may cause the source address of the response to be
different than destination address of the request.
On 10:36 am, sangiova...@nweb.it wrote:
Hello list,
I'm trying to code an SMTP server that stores received messages in a
queue (es. RabbitMQ or Redis).
I'm figuring out how to do it with Twisted, and so far I managed to
print to console the messages the way I want.
I'm trying to understand now
Ron,
Following with interest. Seeking a CoAP Python client capability that
> includes:
> - Support for IPV6 to talk directly to server motes in constrained 6LoWPAN
> WSNs. (the large IPV6 address space is for me intrinsic to the IoT concept)
> - Security for the same, so presumably DTLS.
> Both o
On Fri, Nov 22, 2013 at 8:00 PM, Glyph wrote:
>
> On Nov 22, 2013, at 4:10 AM, Laurens Van Houtven <_...@lvh.io> wrote:
>
> Also, I do really really want the protocol and not the transport. This is
> because I want to pass a reference to the protocol around so that later I
> can call callRemote o
Hello list,
I'm trying to code an SMTP server that stores received messages in a
queue (es. RabbitMQ or Redis).
I'm figuring out how to do it with Twisted, and so far I managed to
print to console the messages the way I want.
I'm trying to understand now how to return a tempfail code (4xx) from