12 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	80a6f7e5ad	Mostly small cleanups and style fixes.	2011-12-13 18:04:43 -08:00
JoelKatz	91f0443e29	Tie application code to master ledger code.	2011-12-13 12:16:17 -08:00
JoelKatz	c891df0ef8	Complete public key cache logic and tie to application object.	2011-12-04 19:32:16 -08:00
JoelKatz	089687152e	The database is not reentrant, so we need a ScopedLock to gate it.	2011-12-02 16:22:10 -08:00
JoelKatz	f3ed8b7ec9	Updates, working to get the network code going.	2011-11-30 21:29:38 -08:00
jed	aa7946dcfd	.	2011-11-03 11:17:06 -07:00
jed	7eae6e5886	added sqllite	2011-10-27 13:04:08 -07:00
jed	880c763dea	.	2011-10-26 16:10:43 -07:00
jed	650ee74391	.	2011-10-20 13:34:49 -07:00
jed	a8e8613475	first	2011-10-14 11:39:06 -07:00