brentashley

Hey, Phil, by all means, don’t squish Squash before it’s had a chance to play out.

I’ve been blogging for a long time now and I’ve been consistently inconsistent. Months of nearly streaming flow followed by weeks of silent ebb. Glorious moments of sharing and collaboration. Rants, observations, laments, odes, screeds.

It’s a bit like a marriage. Just because it changes after a while doesn’t mean that it’s no longer valid, it’s just progressed on to another stage. Stick with it and it will work out well for all concerned.

Phil’s finding new ways to collaborate to make it continue to work – he’s suggesting ensemble blogging. Sounds like a good idea to me.

I’d better not try to extend the marriage metaphor to cover it is all I can say.

My parents live in Parry Sound, a small town on Georgian Bay in Southern Ontario’s cottage country. It’s not a backwater by any means, but not particularly famous for its leading-edge tech community, to be sure.

Imagine my surprise when my friend Shane McChesney pointed me at the Parry Sound website to find a really cool Ajax-driven related-search-results popup that is triggered by selecting any of the text on the page.

As Shane says, this Ajax stuff has certainly crossed the chasm when you find it in such hitherto unexpected places.

Yet another virus is set to cause havok this Friday for Windows users.

Have you heard about the new Unix virus? It comes in source form. All you have to do is visit a website that hosts the virus, right-click and save the file to your hard drive, untar it to a temporary directory, run ./configure, make, make test, then su to root and run make install, then run the program. Poof – you’re infected.

Informit has a very, well, informative article on the BSD family of Unix operating systems.

For over three years now, I have been using OpenBSD for its high security and powerful packet filtering. With a history dating back as far as 1978, BSD is incredibly stable and each branch of it gets more flexible with each release.

The BSD License is much less restrictive than the GPL (used by Linux), which makes BSD attractive to businesses.

On an Exchange server where I have an account, there is a public folder that receives alert messages. I want to collect all the messages in this folder, filter by subject, order by date, and extract text values out of the body of each message. I’d like the output to be delimited text so I can use other tools to perform further analysis, such as loading it into Excel and building a pivot table, or sorting and slicing with any number of tools. I’d like to be able to repeat this automatically.

I started by looking for script examples.

The first ones I found used VBScript under WSH to instantiate the CDO MAPI.Session object, create a Public Folders collection and iterate from there. There are a few different reasons I don’t want to use this approach:

• The machine it runs on needs to have the proper CDO objects on it (pretty well has to be an Exchange server according to the product grid in technote Q171440). I want to run this from any computer that can connect to the server.
• There needs to be a login on that machine with a configured Outlook profile.
• I have an inexplicable aversion to using WSH/VBScript for scripts that may ever run unattended.

The next solution I found used ADODB to query Exchange via the Exoledb datasource.

• again, this object seems only to be on an Exchange server. You have to run it from the same server.

I thought I’d try loading up Outlook on my PC to have a look. It’s installed but I never use it (I use Outlook Express against my main POP3 and OWA against this server). I start up Outlook and go to Tools..Accounts, and select Exchange Server from the wizard.

• It tells me I have to close Outlook and use the Control Panel’s Mail app to add an exchange account to my profile.

After setting it up, I get into Outlook and navigate to the folder. I choose File..Export and try to export to Excel, to Text, to ANYTHING.

• Sorry, that feature not installed. I haven’t got my Office install media with me, so no go.

I have a colleague try from his Outlook and it’s useless because no matter how hard we tried:

• the export process could not include the received datetime field. Not even in the list of mappable fields.

Next, I decided to connect to the server with NNTP or IMAP or POP3.

• These services are all turned off.

Next, I tried to connect to the server’s M: drive which should be an ExIFS filesystem view of the Exchange store.

• It’s not shared out or I don’t have access to that share.

I tried to RDP into the server.

• I don’t have login permissions on the server.

Ok, so ask me what I think of closed systems and protocols. Against any IMAP or NNTP server, I would have been done in 5 minutes with no dependencies.

Well, not really three bears, but it makes a good title.

I’ve been thinking about the history of Web Application Development…

From my perspective, web UI development has traditionally been split into three camps:

• Process: Those who develop the user experience and map business process to web application flow
• Plumbing: Those who develop the elements that store, query and communicate data to and from the application
• Presentation: Those who design the visual elements that comprise the user interface

(Hmmm… they all start with P. Maybe it should have been the three little pigs.)

Each of these camps has a set of requirements and a set of constraints. The constraints of one camp are often offset against the needs of another, causing compromises to have to be reached before an application can be built.

In the beginning, the Plumbing group formatted data into html designed by the Presentation folks and passed it to the browser. Browser interaction was limited to basic population and submission of form elements, much to the chagrin of the Presentation and Process folks.

Porridge 1.0. Yum yum, ho hum.

Along came early (pre-DOM) DHTML. Once the page was rendered, layers could be moved, resized, hidden and displayed. Layer content was difficult-to-impossible to change once rendered. Javascript allowed some form content manipulation. The Presentation people could do some nice animation and acrobatics, but the Process group was left with the constraint that in order to advance through their flow models, it was necessary to refresh the page.

This porridge was too gloopy and didn’t flow nicely.

Some Remote Procedure Call (RPC) capability was introduced in the form of Remote Scripting. This allowed the Presentation group to interact with the Plumbing group to get information from the server and remove the page-refresh constraint from a data perspective, but they still didn’t have enough control of re-rendering the page in place to do much without forcing a visit to the server to rebuild a new page. This caused the Process folks to have to change their single-page flow designs to stretch over multiple wizard-style pages, a necessary but bletcherous compromise.

This porridge was better but still a bit lumpy.

Once DOM-based browsers came along, the elements were in place to satisfy the Presentation group (full manipulation of the rendered page) and the Process group (RPC + UI control). The plumbing guys weren’t happy though, because Remote Scripting either required a client-side Java applet, a non-standard XMLHTTP ActiveX object, or some acrobatic cross-browser hacks using iframes or cookies.

Many people started to build very useful apps based on these elements. These were the people who decided they could live with a browser-specific implementation. Many enterprise apps fell into this scenario, but not many public applications.

This porridge was fairly tasty and getting warm but didn’t have full confidence among the groups.

When IE built XMLHTTP into IE (rather than as an external control) and Mozilla baked its XMLHTTP implementation into its browser, the time was ripe. It wasn’t long until development groups started building rich applications that used it all together.

When Jesse came along and gave it all a name, everyone decided this porridge was ready for eating.

Now we have a zillion flavours of porridge.

With Ajax, the Process, Plumbing and Presentation groups are able to work together with much less friction. Each group’s needs can be met while imposing less constraints on the other groups than before. Many rich applications are being developed which serve as testament to this new ability for the three groups to interact smoothly.

I think some of the most significant advances we will continue to see from here are in the building of abstraction layers that allow modular building of highly interactive apps. The marshaling of complex object data from client to server and back via various serlialization techniques (XML, JSON, etc) has been by and large limited to corporate intranet applications due to performance considerations. With demonstrated tools and techniques that overcome these concerns, newly unified multi-dimensional development groups are already starting to make some very compelling apps that are spilling out of the intranet into the wider Web.

I think weather.com needs to rethink their popup ad campaign strategy this week.

Robert Scoble tells a story about running into Aaron Boodman:

Then Nick introduced us and said “he wrote Greasemonkey.” I answered “I’m not worthy.”

This reminded me of the time I first met Aaron, at the dinner thrown by Adaptive Path and O’Reilly at the end of the first day of their Ajax Summit back in May. I saw him across the room and went over to say hello, since we had had some online interaction in Remote Scripting circles some years ago.

Later, after having dinner seated beside Brendan Eich, creator of the Javascript language and Chief Architect at Mozilla, I saw Aaron coming our way and took the opportunity to introduce the two of them. “Aaron, this is Brendan Eich; Brendan, this is Aaron Boodman”. They reach across me to shake hands, and Brendan says “Wow, Hi Aaron, I love your work!”.

Humble as they come, Aaron was dumbstruck. He managed to stammer “…I think you have that the wrong way around!”, and then they fell into a rich conversation and I slipped away to mingle.