Always online?
Always online? Just discussed with a potential client a mobile data capturing application. The initial idea was just to have a small screen web application. Soon we found out that near the data entry points network coverage is rather patchy. So an offline solution is needed.
I'm considering using either XML/Rest or JMS. The XML approach is tried and tested (think kXML, kSoap) and would resemble a 'classical' sync/replication process. The JMS approach would be more a constant flow of change signals where the JMS would take care of connectivity (or the lack thereof). Joram has kJMS, so that seems like a fit. The big question: how to pipe back changes from the server if there are but no local updates?
I'm considering using either XML/Rest or JMS. The XML approach is tried and tested (think kXML, kSoap) and would resemble a 'classical' sync/replication process. The JMS approach would be more a constant flow of change signals where the JMS would take care of connectivity (or the lack thereof). Joram has kJMS, so that seems like a fit. The big question: how to pipe back changes from the server if there are but no local updates?
Posted by Stephan H Wissel on 03 September 2005 | Comments (0) | categories: Technology