Permalink
Browse files

removing links to old wordpress blog

  • Loading branch information...
izuzak committed Mar 2, 2011
1 parent 663f489 commit ec1c010d454b6d455cff945beaed41b5748398a4
@@ -1 +1 @@
-<meta http-equiv="refresh" content="0;url=/2009/12/14/extending-and-customizing-google-code-project-hosting.html" />
+<meta http-equiv="refresh" content="0;url=/2009/12/13/extending-and-customizing-google-code-project-hosting.html" />
@@ -4,8 +4,6 @@ title: Named arguments in JavaScript
commentIssueId: 2
---
-_(this post was initially published on [my previous blog on wordpress.com](http://izuzak.wordpress.com/), you can visit it [here](http://izuzak.wordpress.com/2009/08/09/named-arguments-in-javascript/) and see the [comments](http://izuzak.wordpress.com/2009/08/09/named-arguments-in-javascript/#comments))_
-
While working on another project (<a title="pmrpc" href="http://code.google.com/p/pmrpc" target="_blank">pmrpc</a>, which I will write about soon), the implementation of a feature came down to calling JavaScript functions with <a href="http://en.wikipedia.org/wiki/Named_parameter" target="_blank">named arguments</a>. Unfortunately, the JavaScript language (or EcmaScript to be exact) <a href="http://ajaxian.com/archives/chrome-extension-api-how-we-wish-we-have-named-parameters">doesn't support named arguments</a>, rather only positional arguments.
<a href="http://www.javascriptkit.com/javatutors/namedfunction.shtml" target="_blank">Usually</a>, JavaScript developers get around this by defining functions to accept a single object argument which acts like a container for all other named parameters:
@@ -4,8 +4,6 @@ title: How to supercharge your free AppEngine quota?
commentIssueId: 3
---
-_(this post was initially published on [my previous blog on wordpress.com](http://izuzak.wordpress.com/), you can visit it [here](http://izuzak.wordpress.com/2009/08/27/how-to-supercharge-your-free-appengine-quota/) and see the [comments](http://izuzak.wordpress.com/2009/08/27/how-to-supercharge-your-free-appengine-quota/#comments))_
-
<a href="http://code.google.com/appengine/" target="_blank">AppEngine</a> is <strong>awesome</strong>! Google's cloud computing platform is hosting countless web apps, from <a href="http://moderator.appspot.com/" target="_blank">Google</a> <a href="http://pubsubhubbub.appspot.com/" target="_blank">products</a> to innovative <a href="http://appgallery.appspot.com/" target="_blank">personal projects</a>, and is constantly being upgraded with cool <a href="http://code.google.com/appengine/docs/roadmap.html" target="_blank">new features</a>. <span style="background-color:#ffffff;">And best of all, AppEngine charges for resources (computing, storage and bandwidth) using a <a href="http://en.wikipedia.org/wiki/Freemium" target="_blank"><strong>freemium</strong></a><strong> </strong>pricing model:</span>
<img class="aligncenter" title="Google AppEngine" src="http://code.google.com/appengine/images/appengine_lowres.gif" alt="" width="115" height="88" /><em>"Each App Engine application can consume a certain level of computing resources for free, controlled by a set of </em><a style="color:#0000cc;" href="http://code.google.com/appengine/docs/quotas.html"><em>quotas</em></a><em>. Developers who want to grow their applications beyond these </em><strong><em>free quotas</em></strong><em> can do so by enabling </em><strong><em>billing </em></strong><em>for their application and set a daily resource budget, which will allow for the purchasing of additional resources if and when they are needed."</em>
@@ -4,8 +4,6 @@ title: A better future for the FriendFeed tools and services ecosystem
commentIssueId: 4
---
-_(this post was initially published on [my previous blog on wordpress.com](http://izuzak.wordpress.com/), you can visit it [here](http://izuzak.wordpress.com/2009/09/02/a-better-future-for-the-friendfeed-tools-and-services-ecosystem/) and see the [comments](http://izuzak.wordpress.com/2009/09/02/a-better-future-for-the-friendfeed-tools-and-services-ecosystem/#comments))_
-
<a href="http://friendfeed.com/fftools"><img class="aligncenter" title="FFtools" src="http://friendfeed-media.com/p-ec49d82ba56b40f7a52b7fc838a84d44-large-1000" alt="" width="75" height="75" /></a><a href="http://friendfeed.com" target="_blank">FriendFeed</a> is the only social-networking application I <em>get</em> and like using, and one of the reasons why is that it's very community-oriented. The <em>groups </em>and <em>friends </em>approach of segmentation of attention easily directs both topic-oriented discussions and friends-oriented discussions towards the right people.
One other nice thing about FriendFeed is that, although not as popular as Twitter or Facebook, it has a healthy ecosystem of developers extending and building upon the platform.  Lots of great <a href="http://wittman.org/projects/friendfeedtranslate/install/index.html" target="_blank">user scripts</a>, <a href="http://ffcheck.com/" target="_blank">bookmarklets</a>, <a href="http://code.google.com/p/feed-buster" target="_blank">feed-processing services</a>, <a href="http://ffsms.com/">sms services</a> and <a href="http://www.ffholic.com/" target="_blank">web apps</a> have been developed and recently even more so with the release of the <a href="http://friendfeed.com/api/documentation" target="_blank">new API</a>.
@@ -4,8 +4,6 @@ title: Inter-window browser communication and how to make it better
commentIssueId: 5
---
-_(this post was initially published on [my previous blog on wordpress.com](http://izuzak.wordpress.com/), you can visit it [here](http://izuzak.wordpress.com/2009/10/10/inter-window-browser-communication-and-how-to-make-it-better/) and see the [comments](http://izuzak.wordpress.com/2009/10/10/inter-window-browser-communication-and-how-to-make-it-better/#comments))_
-
As promised in my <a target="_blank" href="http://ivanzuzak.info/2009/08/09/named-arguments-in-javascript.html">post on named arguments in JavaScript</a>, this post will be about <a href="http://code.google.com/p/pmrpc">pmrpc</a> - a project I've been working on with <a target="_blank" href="http://mivankovic.blogspot.com/">Marko</a> for the last few months.
But first, a bit of background. From mid 2007. when I was interning at Google up until today and my dissertation-related research, an issue that's consistently been popping up in anything I worked on is inter-window communication. <strong>Inter-window communication (IWC)</strong> is the process of transporting data from one window object within a browser to another window object inside the same browser. What's relevant here is that window objects are both full-size windows and iframes - window objects that can be embedded within other window objects (think of an <a target="_blank" href="http://www.igoogle.com">iGoogle</a> page and all the gadgets in it).
@@ -4,8 +4,6 @@ title: Extending and customizing Google Code project hosting
commentIssueId: 6
---
-_(this post was initially published on [my previous blog on wordpress.com](http://izuzak.wordpress.com/), you can visit it [here](http://izuzak.wordpress.com/2009/12/14/extending-and-customizing-google-code-project-hosting/) and see the [comments](http://izuzak.wordpress.com/2009/12/14/extending-and-customizing-google-code-project-hosting/#comments))_
-
<a href="http://code.google.com/hosting/" target="_blank"><img class="aligncenter" style="margin-top:25px;margin-bottom:15px;" title="Google Code" src="http://www.gstatic.com/codesite/ph/images/code_small.png" alt="" width="161" height="40" /></a>
<p>I've used <a href="http://code.google.com/hosting/" target="_blank"><strong>Google Code project hosting</strong></a> for almost every project I've started in the last few years. It's really great and I love both the Web UI and all the functionality-related features (which Google is <a href="http://code.google.com/p/support/wiki/WhatsNew" target="_blank">continuously extending</a>). However, one aspect in which I've found Google Code project hosting<strong> strangely lacking </strong><strong>is customizability and extendability</strong> in adding rich content and even external applications to a project site. Wouldn't it be great if we could add a special "Testing" and "Group discussion" tab or an easy way to embed presentations and JavaScript code into wiki pages? This would boost the usability of project sites and make the visitor experience so much better.</p>
@@ -4,8 +4,6 @@ title: RPC for Web Workers and distributed computing within the browser
commentIssueId: 7
---
-_(this post was initially published on [my previous blog on wordpress.com](http://izuzak.wordpress.com/), you can visit it [here](http://izuzak.wordpress.com/2009/12/21/rpc-for-web-workers-and-distributed-computing-within-the-browser/) and see the [comments](http://izuzak.wordpress.com/2009/12/21/rpc-for-web-workers-and-distributed-computing-within-the-browser/#comments))_
-
<a href="http://ivanzuzak.info/2009/10/10/inter-window-browser-communication-and-how-to-make-it-better/" target="_blank">In a previous post</a> I wrote about <a href="http://code.google.com/p/pmrpc" target="_blank">pmrpc</a> - a project of mine for developing a JavaScript library for <strong>cross-domain inter-window RPC-style communication in HTML5 browsers</strong>. RPC communication is based on two technologies: <a href="http://dev.w3.org/html5/spec/Overview.html#crossDocumentMessages" target="_blank">HTML5 cross-domain messaging</a> as the transport mechanism and <a href="http://groups.google.com/group/json-rpc/web/json-rpc-1-2-proposal" target="_blank">JSON-RPC</a> as the RPC protocol and message format, while the library supports other advanced features (access control, asynchronous calls, retries...). At the end of the post I outlined a few things <a href="http://twitter.com/ivankovic_42" target="_blank">Marko</a> and I wanted to implement next in pmrpc, one of which was support for Web Workers. From the post:
<blockquote><a href="http://www.whatwg.org/specs/web-workers/current-work/" target="_blank"><strong>Web Workers</strong></a> are another specification being developed in parallel with HTML5. The specification “defines an API for running scripts in the background independently of any user interface scripts”. What’s interesting is that the postMessage API is used to communicate with web workers and therefor pmrpc could be extended to include support for web workers.</blockquote>
Well, the API used to send messages from a web page to a worker and vice versa is not exactly the same as the cross-document messaging API, but is very similar. So, the idea for supporting Web Workers was leave the <a href="http://code.google.com/p/pmrpc/wiki/PmrpcApiDocs" target="_blank">pmrpc API</a> for registering, calling and unregistering procedure unchanged, and just extend it to also use the Web Worker API for message transport (in addition to the cross-doc messaging). And about two weeks ago we released <a href="http://code.google.com/p/pmrpc/downloads/list" target="_blank">a new version of pmrpc</a> with Web Worker support. Here's an example of <strong>using pmrpc with Web Workers</strong>:
@@ -4,8 +4,6 @@ title: Real-time feed processing and filtering
commentIssueId: 8
---
-_(this post was initially published on [my previous blog on wordpress.com](http://izuzak.wordpress.com/), you can visit it [here](http://izuzak.wordpress.com/2010/01/11/real-time-feed-processing-and-filtering/) and see the [comments](http://izuzak.wordpress.com/2010/01/11/real-time-feed-processing-and-filtering/#comments))_
-
<em>This is another lengthy post so I'm writing a brief overview as an introduction.</em>
<h2>Introduction</h2>
This post is about web syndication feeds (RSS and ATOM), technologies for real-time delivery of feeds (PubSubHubBub, RSSCloud) and two opportunities I believe could help make these technologies better and widen their adoption: <strong>real-time feed processing/filtering and end-user selection of processing/filtering services</strong>. First, I'll write about my experience with polling-based feed processing services from developing Feed-buster, a feed-enhancing service for use in FriendFeed. Next, I'll give a short overview of PubSubHubBub (PSHB) and several ways of integrating feed filtering and processing functionalities into the PSHB ecosystem without changing the PSHB protocol. Lastly, I'll try to argument why there should be a better solution and outline an idea for an extension to the PSHB protocol.
@@ -4,8 +4,6 @@ title: Why understanding REST is hard and what we should do about it - systemati
commentIssueId: 9
---
-_(this post was initially published on [my previous blog on wordpress.com](http://izuzak.wordpress.com/), you can visit it [here](http://izuzak.wordpress.com/2010/04/03/why-understanding-rest-is-hard-and-what-we-should-do-about-it-systematization-models-and-terminology-for-rest/) and see the [comments](http://izuzak.wordpress.com/2010/04/03/why-understanding-rest-is-hard-and-what-we-should-do-about-it-systematization-models-and-terminology-for-rest/#comments))_
-
<em>This is going to be another long post, so I'm using the introduction as an overview again.</em>
<em><span style="font-family:Verdana;font-style:normal;line-height:normal;"> </span></em>
@@ -4,8 +4,6 @@ title: Pmrpc discovery and publish-subscribe support + systematization of cross-
commentIssueId: 10
---
-_(this post was initially published on [my previous blog on wordpress.com](http://izuzak.wordpress.com/), you can visit it [here](http://izuzak.wordpress.com/2010/06/15/pmrpc-discovery-and-publish-subscribe-support-systematization-of-cross-context-browser-communication-systems/) and see the [comments](http://izuzak.wordpress.com/2010/06/15/pmrpc-discovery-and-publish-subscribe-support-systematization-of-cross-context-browser-communication-systems/#comments))_
-
The <a href="http://code.google.com/p/pmrpc/" target="_blank">pmrpc</a> cross-context browser communication library has grown from the <a href="http://wp.me/poYaf-44" target="_blank">last time I blogged about it</a>. Last time I wrote about adding support for RPC-style communication for <a href="http://www.whatwg.org/specs/web-workers/current-work/" target="_blank">WebWorkers</a>. Today I'll first introduce two new features - dynamic <strong>discovery of remote procedures</strong> and a<strong> publish-subscribe communication model</strong>. Also, I'll write about our <a href="http://code.google.com/p/pmrpc/wiki/IWCProjects" target="_blank"><strong>systematization of existing systems for cross-context browser communication</strong></a>.
<h2>Discovery and publish subscribe</h2>

0 comments on commit ec1c010

Please sign in to comment.