Neale Upstone

Current implementation for the embedded client doesn't allow multiple threads query simultaneously. This will only happen when using TCP/IP support. Instead, it would be worth considering what is standard for...

For simplicity of not storing information in multiple locations, we want to be able to take an input such as a postcode, and have it's ECEF vector available internally for...

see http://engineering.twitter.com/2011/08/finagle-protocol-agnostic-rpc-system.html

We currently serialize by default. We could instead provide an abstraction to allow any encoding scheme to be used for net and disk I/O. This could be a safe stepping...

Some checks could be done within the client implementation to ensure that a persisted object is never shared between multiple threads.

Currently using SyncedAttrDefinitionMgr during store init, and then CurrentTxADM when using the database. Need to provide a working current tx AttributeDefinitionService that eliminates the need to pre-configure anything but the...

Current situation is that if we have an arbitrary detached object, it has no idea what instance of that entity it is. It needs it's @Id field, or to implement...

This could be a big (ish) change. We have options: 1) Expose the data on the server. We'd need to allow create, update and delete to send an UpdateCmd() to...

SynchedAttributeDefinitionMgr is clumsy to say the least, and relies on it's plural and on quirky refs. We need a replacement or refactor that allows whatever is going on to properly...

This would create a Mockito mock and place it in the context to be autowired everywhere. ``` @Autowired @Mock private DataOperations mockToProvideToSpringContext; ``` This would spy (where possible) on a...