9 Commits

Author	SHA1	Message	Date
JoelKatz	639ba9dfcb	NetworkOPs layer ... Begin coding the 'NetworkOPs' layer. This will provide most of the functions 'client' code will want to call such as functions to lookup transactions, check on their status, get balances, and so on. Much of the RPC layer will be a thin wrapper over these functions. The purpose of this layer is to permit the node to support these functions regardless of its operating mode or available data, as long as it's connected to the network. If synchronized and tracking the current ledger, it can do most functions locally. If not, it can ask for help from other nodes. If hopeless, it can return an error code.	2011-12-15 01:19:50 -08:00
JoelKatz	0b25b9641f	Fire up the initial ledgers and attach them to the application.	2011-12-13 21:54:17 -08:00
JoelKatz	4b5bc85a0d	More work on ledger sequencing: ... Track whether ledger is accepted. Assert on modifications to an accepted ledger. Save accepted ledgers to DB. Load ledger by hash/index. Ledger history functions, ledger canonicalization. 'Push' ledger to history.	2011-12-13 18:05:29 -08:00
JoelKatz	263fe6f515	Begin merging this code.	2011-12-13 12:17:51 -08:00
JoelKatz	1d140e8829	Sync Linux tweaks.	2011-11-07 13:45:32 -08:00
jed	11a964ffed	.	2011-10-21 11:32:23 -07:00
jed	0416d64fdc	.	2011-10-20 16:34:22 -07:00
jed	650ee74391	.	2011-10-20 13:34:49 -07:00
jed	a8e8613475	first	2011-10-14 11:39:06 -07:00