| shenapmzsc | Date: Monday, 05 Aug 2013, 14:11:58 | Message # 1 |
|
Private
Group: Users
Messages: 5
Status: Offline
| <a href=http://www.wholesale-oakleysunglasses.us/new-oakley-frogskins-sunglass-orange-and-blue-frame-yellow-lens-p-112.html>New Oakley Frogskins Sunglass Orange And Blue Frame Yellow Lens</a>
<a href=http://www.wholesale-oakleysunglasses.us/new-oakley-radar-black-frame-blue-lens-sunglass-p-238.html>New Oakley Radar Black Frame Blue Lens Sunglass</a>
<a href=http://www.wholesale-oakleysunglasses.us/new-oakley-frogskins-sunglass-colorless-frame-navy-blue-lens-p-113.html>New Oakley Frogskins Sunglass Colorless Frame Navy Blue Lens</a>
A developer buddy of mine a short time ago started at about a new company one of his tasks could be to developed a new web application allowing you their users to function offline when their staff are onsite in remote locations after which they later to sync getting a server side database that they haven't yet yet determined a web server side provider yet (i'm guessing it may be SQL Server).
HTML5 Offline Data Storage Options
There is certainly a browser explosion happening with smartphone adoption, so its difficult to work out how much of the market supports HTML5 LocalStorage features but using statcounter As a former in the position to calculate that between Chrome (4+), Firefox (3.+), Safari (4+), Opera (10.5+) and IE (8+), including iPhone and Android devices you should have captured around 8085% of these market, keeping this figure going upwards an interest rate of 12% 4 weeks. Others in the industry being IE 6/7 (which stubbornly will usually hang on), older versions of recent browsers (with update features that generally kept them current), as well as having mobile browsers stuck back in the stone age. If you carry out like to venture down this road, however, Lots of you make an examination of PersistJS for the guys who assemble it did nearly all of the tasks you'll have to already.
I did some shopping around which amounts to just two viable choices are LocalStorage and IndexedDb, with LocalStorage being the widely known technology? May be go HTML5 and all fine and dandy, but long story short my question(s) is/are.
Any intelligent evidence based replies probably will get my upvote so don't merely rush to find the first answer and work to score some quick points, I'm trying to get the right solid feedback here. Appreciate it.
IndexedDB has become overengineered (individually) and isn't widely supported (yet) whatsoever Mozilla's insistence its as good as sliced bread, and WebSQL's future looks quite a bit uncertain as Mozilla is refusing to utilise it and its never being completed caused by an impasse between W3C along with browser vendors that have actually implemented it (Chrome/Safari/Opera).
what some things that maybe your organisation does that operates, as well as what doesn't work?
In these modern times its more vital anticipating (as current market may be like in 12 years time whenever your app is propagating and gaining a good users list) than backwards, so I'd say HTML5 LocalStorage is in all likelihood a good solution.
http://www.china-oil-arts.com/karenmillendressireland.asp
|
| |
| |
