Profile cover photo
Profile photo
Glenn Jones
Exploring ideas of the semantic web and data portability
Exploring ideas of the semantic web and data portability

Glenn's posts

Post has attachment
Animated Photo

Post has shared content
More AppCache problems - it is a douchebag of an API
We've recently just released a new HTML 5 web app that follows the single page app design and are using App Cache to enable a certain amount of offline functionality.  However most data is fetched from a cross origin RESTful API in which we allow access to via the NETWORK element in the App Cache manifest file.

In order to secure the data being transferred from the app to the API we want to ensure all calls to the API are made securely using SSL.  When we change the protocol for the URL of the endpoint and update the NETWORK white-list to we find in Chrome that it kills the request off.  The request never makes it outside of the browser.  Testing in desktop Firefox appears to not experience the same behaviour.

It appears the if we make the NETWORK element a full wildcard then Chrome is happy and our requests make it out of the browser.  However I'm unhappy to implement this as a fix as it's unclear if in doing so we risk having the application load all resources from the network even if previously we had asked it to cache them through the App Cache CACHE directive.  From a security perspective whilst we would achieve securing the data transfer between the web app and the RESTful API we would open up another security hole by allowing any script network access to download whatever content it likes.

At the moment I want to understand if this is a bug just in Chrome, or if we're doing something that App Cache wasn't designed for.  I'll update you as my journey unfolds as we dig further.

#html5 #appcache #'CORS

Post has attachment
I have just released a brand new microformats 2 parser for node.js.

Demo API

Try the API with:

About microformats 2

The blog post link gives a bit more of an overview. I hope this work will help microformats and the concept of the semantic web move forward another little step. Enjoy

Post has attachment
From todays walk on the south downs - great day to be walking

Post has attachment
I have just uploaded a new version of microformat-node. The parser now takes between 30-40 milliseconds to parse an average page, about 8 times the speed of the last version. 

Features of new version
* About 8x faster at parsing 
* Will now load onto Windows based hosting solutions correctly
* Inbuilt cache system, which can be customised
* Upgraded logging and trace options
* Upgraded unit test system
* Added support for JavaScript promise


I have changed how the method calls work so if you are using it you may have to update your code. The parse methods parseHtml and parseUrl now follow the standard pattern used in node.js and return an error and data object rather than just the data object.

Post has attachment
I have just released a new node.js microformats parser. It is based on
the javascript microformat-shiv project, which is used to build browser
extensions and web apps.

It currently supports the following formats: hCard, XFN, hReview,
hCalendar, hAtom, hResume, geo, adr and tag. I have not built
microformats v2 support into it yet.

The project page:
Source code:
Test server :

Post has attachment
From todays brighton to lewis walk across the south downs

Post has attachment
Just uploaded new/updated collection of browser File and Clipboard API demo's

Post has attachment
The new home of the Chromebook Google gave me. Sits nicely in the couch, for web browsing. Thinking about the wider product feedback for the chrome team. 
Wait while more posts are being loaded