My newest Internet Computing column is now available (PDF). This time around, I talk about reflection, which of course has been around for ages but has recently been growing in popularity because of the flexibility it affords, even though using it often means more complicated code. Comments on the column welcome, as always.
Middleware Matters |
|
Steve Vinoski's Weblog
Search
About
This page contains a single entry from the blog posted on January 22, 2005 11:41 PM.
The previous post in this blog was When an EPR fails.
The next post in this blog is EPR metadata.
Many more can be found on the main index page or by looking through the archives.
Powered by
Movable Type 3.31
Movable Type 3.31
Comments (1)
Interesting and timely article. I am trying to finish up a presentation describing WS-* as a massive federated reflection architecture, which inherits many of its reflective properties from proto-reflective concepts first applied in Internet protocols (IP headers as reflective metadata, RFC 822 email headers as reflective metadata), then in Web protocols (HTTP/MIME headers as reflective metadata, HTML/DOM as reflective metadata).
In fact HTML/DOM provides practical everyday examples of reflective programming that goes unnoticed. Look at bookmarklets, e.g., a bookmarklet that changes all links to "open in other window" links. And check out Greasemonkey for Firefox, which gives you powerful ways to transform received web pages, e.g., to fix non-standard tags.
-- Nick
Posted by Nick Gall | January 23, 2005 5:55 AM
Posted on January 23, 2005 05:55