- From: Nikunj Mehta <nikunj.mehta@oracle.com>
- Date: Sat, 21 Jun 2008 16:21:19 -0700
- To: Maciej Stachowiak <mjs@apple.com>
- CC: Arthur Barstow <art.barstow@nokia.com>, public-webapps@w3.org
The paper states it clearly - ... applications are also required to use a SQL-based programming model to take advantage of the local storage capabilities requiring the application to be rewritten to acquire off-line capabilities. ... applications locally store a transformation of online that is better suited to local processing in a local database, e.g. a local relational database. Applications must then employ a data switch between on-line and off-line operation, explicitly accessing the local database only when off-line. The problem with this approach is that the application devolves to two separate applications that are each accessible with the same UI. Worse, the application-specific data transformation can make it harder to perform application-independent synchronization. There is no HTTP access model for local data in HTML5. The ability to interpose a synchronized cache other than the browser's own is missing in HTML5. Therefore, an application cannot transparently switch to a local data model - that choice as well as the burden of synchronization is entirely on the application programmer. Nikunj Maciej Stachowiak wrote: > > On Jun 21, 2008, at 12:13 AM, Nikunj Mehta wrote: > >> Hi Art, >> >> Here's a paper that describes the use cases and requirements about >> AtomDB. It does not include API details, although if you find this >> interesting, we can proceed to that next. >> >> I look forward to reading comments and getting feedback from the >> community > > I would appreciate a summary of what AtomDB provides that is not > covered by the offline features of HTML5. If there is indeed > interesting new functionality, I would like to understand how it can > work in concert with HTML5 features such as the application cache. > Would AtomDB be a competing technology or a complementary technology? > > Regards, > Maciej > >> >> >> Thanks, >> Nikunj >> Arthur Barstow wrote: >>> Nikunj - perhaps it would be helpful if you provided some additional >>> information/pointers regarding AtomDB e.g. use cases and >>> requirements, the architectural model, API, comparison/gaps versus >>> related functions in HTML5, etc. >>> >>> -Regards, Art Barstow >>> >>> On Jun 11, 2008, at 5:11 PM, ext Nikunj Mehta wrote: >>> >>>> >>>> We are familiar with the offline persistence capabilities of HTML5 >>>> and their support in browser implementations. Oracle's AtomDB and >>>> related specification are about transparent, read-write caches that >>>> are auto-synchronized using Atom publishing protocol. >>>> >>>> I hope this makes clear the intent of my original email. >>>> >>>> Regards, >>>> Nikunj >>>> >>>> Maciej Stachowiak wrote: >>>>> >>>>> >>>>> On Jun 11, 2008, at 1:47 PM, Nikunj Mehta wrote: >>>>> >>>>>> >>>>>> Hi Art, Charles, >>>>>> >>>>>> We have developed a technology, called AtomDB, at Oracle for >>>>>> transparent, local access to Web application resources when not >>>>>> connected to a network. This is one of the most frequently >>>>>> requested features on our mobile applications, which until now >>>>>> has required a non-Web application solution. Oracle is interested >>>>>> in developing Web applications for mobile and non-mobile >>>>>> environments that are resilient to network unreliability. >>>>>> >>>>>> In the process of developing AtomDB, Oracle has analyzed various >>>>>> challenges in off line data access. We realize that the Webapps >>>>>> WG is interested in this area and Oracle is willing to contribute >>>>>> resources to advance specifications that improve application >>>>>> robustness to network conditions. We have a specification that we >>>>>> could share with the WebApps WG, if there is interest. >>>>>> >>>>>> I look forward to what the working group has to say on this. >>>>> >>>>> HTML5 includes mechanisms for offline applications and offline >>>>> data. The application cache is implemented in the Firefox 3 >>>>> Release Candidate and the Safari 4 Developer Preview: >>>>> >>>>> http://www.w3.org/html/wg/html5/#offline >>>>> >>>>> Database storage is in Safari 3.1 and newer: >>>>> >>>>> http://www.w3.org/html/wg/html5/#sql >>>>> >>>>> >>>>> Google Gears also has features similar to both of these and I >>>>> believe those features are planned to converge with the standard. >>>>> >>>>> Regards, >>>>> Maciej >>>>> >>>>> >>>> >>>> >>> >>> >> >> <Going far without the bars.pdf> > >
Received on Saturday, 21 June 2008 23:23:01 UTC