Sorry, I've looked everywhere but I can't find the page you're looking for.
If you follow the link from another website, I may have removed or renamed the page some time ago. You may want to try searching for the page:
Sorry, I've looked everywhere but I can't find the page you're looking for.
If you follow the link from another website, I may have removed or renamed the page some time ago. You may want to try searching for the page:
I've done a courtesy search for the term for you. See if you can find what you're looking for in the list below:
Cloud computing has largely passed through it's hype phase - that period where all kinds of magical characteristics are applied to it because no one really knows that much about it, and is shifting to the real world scenarios where people are actually building clouds and finding the limitations therein (and the cycle goes through the Trough of Despair).
Despite this incipient skeptical phase, there are some significant reasons to think hard about the combination of cloud computing and XML Databases, especially those such as MarkLogic or eXist-db that combine the database with a web app server. There are many ways of using such servers, though I believe one of the most powerful is to use a RESTful Services approach in conjunction with URL rewriting in order to create intelligent file systems.
Michael Kay recently covered common mistakes made using XSLT, which made me think it maybe useful to do the same treatment with XQuery. A lot of the points Michael Kay raised in his article also directly applies to XQuery, that is:
In no particular order of importance I present the most common errors I see users make when learning XQuery.
There is a whole class of mistakes related to developers insisting on using the FLWR structure in a free form way, that is use For, Let, Where, Order or Return in any kind of order.