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.
As yet another indication that publishing is shifting to the eBook world, O'Reilly Media is in the process of putting together a version of their popular HTML 5/XHTML Reference book specifically for Apple's iPhone/iPad. It will also work with Google's Android operating system, though the beta is still a little buggy there. Pay attention on what kind of hit count they get from these mobile devices.
Computer reference books actually make remarkably good fodder for mobile hand-helds as eBooks; they are generally structured as discrete topics rather than continuous narratives, and if you're coding on a laptop or desktop and need to look up an API call or how a particular tag is utilized, having your iPhone, Android or Kindle sitting as a quick finger stroke reference could prove very useful. For more information, check out their beta site at http://htmlref.labs.oreilly.com/.
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.
To a certain extent, I think those people that are looking to get XQuery into the browser are tilting at windmills, and frankly are wasting their time. It's not that I don't see advantages to having browsers be XQuery aware - far from it. The ability to both manipulate the DOM and to manipulate external data resources using XQuery would dramatically simplify a lot of the code written in JavaScript. The problem is that the JavaScript does exist, is in wide usage, and I see a language like Python or Ruby making its way into the browser before I see XQuery doing so. Building a JavaScript-based Xquery system is probably the cleanest approach to getting that support, but even that's probably a fool's errand.
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 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.
Published originally on 2010-07-23.
Yesterday, a tweet, from @jirkakosek, reminded me that I needed to mention a recent bit of work I got done using the impressive oXygenXML XML editor.
Over the later part of last year and early part of this year I had collated a series of small recipes I had been gathering for a modest little book (Ant Recipes for Web Developers). These recipes were just simple little snippets of how to subvert Apache Ant to do common web related software development tasks. I thought that with me spending most of my time on XProc I had to 'clear the decks' with previous technologies ... I had used Apache Ant for many years for many of the things that XProc is purpose built to do.