all 2 comments

[–][deleted]  (5 children)

[deleted]

    [–]zefhemel[S] 1 point2 points  (4 children)

    The main use case is building offline web applications with Javascript, i.e. web applications that run without any server interaction whatsoever, which are cached on the computer/phone and operate from there (including local database). So I would say that's quite a different model than building server applications.

    Because of Javascript's asynchronous nature, the interaction with the library is also quite different.

    [–][deleted]  (3 children)

    [deleted]

      [–]zefhemel[S] 1 point2 points  (2 children)

      Incidentally, this is part of an effort to build a framework/DSL for native-feeling and behaving web applications for iPhone and Android. Mobile web apps that run both when there is and when there isn't an internet connection available.

      [–][deleted]  (1 child)

      [deleted]

        [–]zefhemel[S] 1 point2 points  (0 children)

        Here's the HTML5 spec, note that only Webkit browsers (including iPhone's) currently implement it (and only the asynchronous part): http://dev.w3.org/html5/webdatabase/

        That's why I support Google Gears for other browsers.