… | |
… | |
6 | |
6 | |
7 | faq: can't se anything |
7 | faq: can't se anything |
8 | faq: all is asynch |
8 | faq: all is asynch |
9 | faq: how to interface to non-perl nodes? |
9 | faq: how to interface to non-perl nodes? |
10 | |
10 | |
11 | TODO: optimised json transport jsonxyz#d# |
11 | TODO: maybe disbale warnings by default? |
|
|
12 | |
|
|
13 | - listener-less nodes had trouble sending keepalive |
|
|
14 | messages on write timeouts (found by Sadrak). |
|
|
15 | - the monitor guard could cause a memleak due |
|
|
16 | to autovivification if a mon was cleared after |
|
|
17 | the port was gone (analysed by Sadrak). |
|
|
18 | |
|
|
19 | 1.28 Thu Apr 1 21:23:54 CEST 2010 |
|
|
20 | - accepted conenctions didn't corretcly set up the SRCNODE |
|
|
21 | in some cases, leading to intra-node messages (such as monitoring) |
|
|
22 | to fail silently (great testcase by Sadrak). |
|
|
23 | |
|
|
24 | 1.27 Sat Mar 20 21:11:16 CET 2010 |
12 | - avoid exceptions in the transport code if the connection |
25 | - avoid exceptions in the transport code if the connection |
13 | fails during TLS negotiation. |
26 | fails during TLS negotiation. |
14 | - delay new address broadcasts in seednodes, to reduce the |
27 | - delay new address broadcasts in seednodes, to reduce the |
15 | likelyhood of nodes connecting at the same time, leading to |
28 | likelyhood of nodes connecting at the same time, leading to |
16 | message loss. |
29 | message loss. |