b8546e28af
Moving "Security" to a separate port, so there can be a Bouncycastle and a Spongycastle implementation. (BC doesn't work on Android, SC can't be used on Oracle's JVM)
2015-08-05 19:52:18 +02:00
7f4c67f43e
Removing IV of received objects from requested objects list (I forgot that one)
2015-07-03 07:56:18 +02:00
2c4d95af2f
smarter network code, fixed various issues
...
- deciding on the stream at creation time is just silly - it should be done based on the identities (this part is TODO)
- changed NodeRegistry so it doesn't store nodes - this should help to connect faster
- inventory items shouldn't be advertised to nodes that are already aware of them (issue #13 )
- objects shouldn't be requested more than once (issue #9 )
2015-07-01 06:57:30 +02:00
884171fe18
issue #15 : fixed socket timeouts and connection shutdown - no exceptions should be thrown if the network node is being shut down, although it can take up to 5 seconds = max(READ_TIMEOUT, CONNECT_TIMEOUT)
2015-06-24 22:56:17 +02:00
6be8d51f6d
Distributable JAR build
...
- connection manager should now be rock stable
- does try to create new connections as long as there are less than eight active connections, which might result in more than eight outgoing connections, but this shouldn't be a problem
- some minor improvements and bug fixes
2015-06-18 13:41:11 +02:00
1dc4582012
Issue # 5: fixed test and initialisation
2015-06-17 06:23:00 +02:00
9b0de83706
Issue # 5: initialize node repository if there are no nodes in DB
2015-06-17 06:00:03 +02:00
c0a7acc609
Greatly improved network code - the "manage the node repository" part of issue #5 should now be OK
2015-06-16 06:41:59 +02:00
ed0d1c2911
issue #4 : prevent connections to self, select random nodes to connect to
2015-06-13 17:37:55 +02:00
bd5bf76904
Improved connection management, preventing multiple connections to the same node, and improved broadcast handling.
2015-06-12 06:57:20 +02:00
b4683bba68
Broadcasts. Receiving seems to work, but there still seems to be a problem with sending them.
2015-06-09 22:45:24 +02:00
274c16b748
Implemented sending messages (and fixed a few bugs on the way)
...
This closes issue #3
2015-05-29 13:17:00 +02:00
c7542e438f
Ignore this test - it's pointless anyway
2015-05-26 17:54:04 +02:00
245ca22743
Updated documentation, added German translation
2015-05-24 21:55:37 +02:00
b793526f2f
Inventory items are now saved only if processing didn't fail. Receiving messages works, but there seems to be a problem with the POW check in some circumstances.
2015-05-23 10:27:05 +02:00
1fbc4a1d74
Major refactoring
2015-05-19 19:16:20 +02:00
a65907f13b
Some work on addresses and private keys that still doesn't work. As a side effect, sending objects now works basically.
2015-05-01 17:14:43 +02:00
00bd6a08b7
Added SerializationTest for object payload (which is probably the most important)
2015-04-28 18:36:07 +02:00
f00c6018e7
Some refactoring
...
- I didn't like the way the context was initialized
- The DatabaseRepository got too complicated
2015-04-24 11:11:08 +02:00
51c1ecfd41
Minor refactoring
...
I think having the read method in the same place as the write method might help preventing some errors
There are some people who are strictly against using static methods. I suppose I'm not experienced enough yet.
2015-04-18 16:44:00 +02:00
e611e5e20a
More or less properly shutdown client / network node
2015-04-17 13:01:46 +02:00
32de01bbf5
Some basics seem to work now like storing messages, addresses, inventory vectors etc.
2015-04-14 19:47:53 +02:00
35088ca033
Network code now works well enough for the server to think it successfully established a connection
2015-04-07 18:48:58 +02:00
3299d8ca4a
Networking code, untested
2015-04-06 10:01:03 +02:00
0c4b39bdee
It's now possible to send a 'version' message that will be accepted by the other node.
2015-03-31 21:06:42 +02:00
