Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • Why don't you construct a prototype purposed for identifying potential blocking factors? Seems to be a much more practical approach than trying to identify the set of all potential problems and the set of all potential solutions. What kind of problems? Human, code, redis, algorithm performance, key/value queries in general, practical, theoretical, etc. This seems to me to be a question with infinite answers. Commented Nov 29, 2011 at 19:49
  • It would be handy to have some background information on potential problems before starting to work on prototype (and to know if it would be reasonably feasible). I'm interested namely in querying aspects and some theory since this is a completely new area for me. Commented Nov 29, 2011 at 19:56
  • 1
    I recently dealt with HTML5 offline storage, a new area for myself. While the W3C documentation and Apple training videos helped me, I did not get a real grasp for various issues until I actually built a prototype. For example, the fact that key/value pairs are far more difficult to perform complex queries (if not impossible) as compared to the SQL version of offline storage which allows joins and such. Other, oddball issues came up like one of the standards is actually being discontinued by W3C. Most of these issues simply surfaced in the research necessary to get the 2 prototypes to work Commented Nov 29, 2011 at 20:01