Create RemoteDAO interfaces for specific remote client platforms

[GoogleCodeExporter]

Have a single base RemoteDAO that is called from separate thin classes that 
expose the functionality remotely.

For example the RemoteDAO would provide a method find(Class<?> klass, 
Serializable id). The interface class for Flex would provide a method 
find(String className, Serializable id) that is called directly from Flex.

This way if some of the methods or parameters are not usable for a 
particular technology, a workable interface class could be customized for 
that technology.

Original issue reported on code.google.com by dwolvert on 1 Dec 2008 at 8:29

[GoogleCodeExporter]

This was addressed in 0.3.4. The solution was to have a totally separate 
RemoteDAO 
for each technology. The behavior of using to specific or general DAOs was 
delgated 
to another DAODispatcher class that can be shared by all the various remote 
DAOs. The 
remaining implementation of the methods in the remoteDAO (now called a remote 
DAO 
adapter) is now fairly trivial.

Original comment by dwolvert on 16 Dec 2008 at 7:37

• Changed state: Verified