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.
Editor Note: This was first publishing Nov. 23, 2009.
And no. I'm not going to start out with "It was the best of times, it was the worst of times". But I will tell you what kind of time it was.
It was a big damn Gold Rush.
As gold rushes tend to do, it made a mess of a lot of things; some got rich and most didn't, and those who were already wealthy figured out how to take advantage of the situation. And there's one other major thing that gold rushes do: they tend to tilt balances.
Editor Note: This was first published on Nov. 23, 2009.
Here at XML Today there is a strong and laudable push to promote XRX architecture. However, the very loosely defined REST architectural style leaves us a little short on best practice recommendations.
REST is usually presented as "Many nouns, few verbs," with the assumption that, because we know the verbs inside and out, we're going to save time and write simpler code. But really, we don't - we can't - know all of the HTTP verbs as thoroughly as we'd like.
Grappling with that particular problem yields one very basic architectural concept, the Discrete Resource. The characteristics of the Discrete Resource follow pretty naturally from consideration of the HTTP methods GET, PUT, and DELETE.
Editor Note: This was first published on May 31, 2010.
Some time ago I tweeted on the observation that Information Technologies tend to be destructive to jobs overall, and was rather surprised at the number of responses I received to that comment. As I've found that trying to argue a thesis that broad over Twitter can be an exercise in Haiku minimalism, the post came into being to explain a bit more my thinking here, and to suggest that IT's influences are THE primary engine driving the nature of work in the 21st century.
Editor Note: This was originally published Feb. 10, 2010.
Over the weekend, a client of mine was hacked, part of what seems to have been a broad, rootkit based attack that took out a number of sites in what appeared to be prep work for zombification of servers for spam delivery. I won't give out the details of this particular incident, as we're still trying to figure out the exact exploit, but it brought to light a few facets of emergency preparedness that should be thought about when dealing with XML databases in particular.
Editor Note: This was originally published 30 October 2009.
One of the more problematic issues involved with working with XML Databases is what may seem to be relatively simple - getting files into the database in the first place. This was one of the challenges that was put to me by Dan McCreary for a series of open source applications that he's developing around the eXist XML database as part of his efforts with Syntactica. While you can use WebDAV (and in general probably should for production level work), a generalized file uploader web app is also possible, and serves to illustrate how you can actually create some very powerful tools with application vendor augmented XQuery. Note that the examples given here are all built around the eXist-db XML Database. It's definitely possible to do similar applications using the MarkLogic database, though I'll leave this as an exercise for a future article.