On May 30, 6:14 am, JamesU <[EMAIL PROTECTED]> wrote:
> Hi there,
>
> I've been experimenting a bit with the iPhone simulator in the SDK to
> see if i can make web-based apps that can work off-line.
>
> Consequently i've ended up using the "data:/" URL "hack". But i've
> noticed that this is pretty useless apart from quick utility apps
> (like a calculator).
>
> Looking further, i noticed that there is client-side database support
> in the simulator's browser. So naturally, i thought "can i combine
> data:/ URL's and the database API to make a useful offline app?".
>
> So i took one of the simple database examples and converted it to a
> data:/ URL (http://webkit.org/misc/DatabaseExample.html). And it
> seems to work rather nicely - i can create notes, close the page, open
> it again, and see the notes i previously created. In addition i can
> access the notes from any other "data:/" URL, which seems quite neat.


James,  Any chance you can share your data:/ source code?

Thanks,
JP
>
> Thinking about it, in theory i could store "data:/" URL's for extra
> images in a client-side database, allowing me to significantly cut
> down the size of my app's main "data:/" URL.
>
> Now my question is this: Are there any really obvious limitations on a
> real device in combining "data:/" URL's and client-side databases?
> I've noticed that supposedly database access is restricted per-domain,
> but this does not seem to apply to "data:/" URL's. Looking at Safari
> on my mac for example, "data:/" URL's are all grouped under one tree
> in the security preferences.
>
> Any insight or further suggestions would be appreciated.
>
> ~ James

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"iPhoneWebDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/iphonewebdev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to