Hello. I am Paul Kinlan.

I've figured out how to incorporate OPML into the upcoming version of the AJAX Tagger, enhancing its functionality. More details coming soon!

Just a quick update on what I've been up to. I'm still working on AJAXTagger v2 whenever I can. It's coming along, but I ran into a few JavaScript issues. Big shoutout to the Dream Projections blog for a post that really helped me figure out how to call JavaScript Object methods with setInterval – super useful for the priority queueing system I'm building.

I just cancelled my Xbox Live account after 3 months of not using it, mainly due to a poor internet connection with Wanadoo. The cancellation process was quick and easy, taking about 2 minutes. I might consider subscribing again when the Xbox 360 comes out.

I'm seeking feedback on the AJAX Tagger I've implemented in my journal entries, specifically concerning the Wikipedia article links. Are they useful? Do you have any suggestions for improvement? You can email me at paul.kinlan@gmail.com or leave a comment.

I'm exploring ways to implement continuous polling of a resource and event dispatching based on its state in JavaScript. Are worker threads, or something similar, achievable in JavaScript? Currently, timer-based triggers seem like the most viable option. Is this an acceptable approach, or are there more efficient and appropriate alternatives?

This post kicks off documenting the requirements for the next version of AJAXTagger. The goal is to create a successful application (by my definition) by outlining features across functional areas, UI/UX, client/server-side business logic, data access, and dependencies. Key features include easy journal tagging, related information retrieval (tags, articles, blogs, websites), diverse search provider integration, streamlined results presentation, image inclusion, and efficient article pulling/saving. The UI should minimize user effort, provide immediate feedback, and offer information hiding. Performance is crucial, targeting IE6/7 and Firefox, with emphasis on minimal server round trips, client-side optimization, and error handling. Data storage is preferably client-side, with external access optimized for speed and resilience. External dependencies include various search engines/services, while internal constraints involve limited server access and reliance on HTML, JavaScript, and XmlHTTPrequest.

I've always struggled to find good directories of companies offering web services. I finally stumbled upon ProgrammableWeb (http://www.programmableweb.com/apis), which has a pretty good list of major web APIs. However, it also highlights the disappointing scarcity of companies providing decent APIs for developers.

I just watched an exciting Channel 9 video about the future of C# 3.0, featuring Anders Hejlsberg. It highlighted some game-changing features, including extending classes with new methods without derivation and the introduction of Lambda functions. One particularly cool feature is the addition of LINQ (Language Integrated Query), which extends IEnumerable objects with SQL-style operators. I'm still exploring how I can use this in my own projects, but it looks incredibly promising!

I've fixed a bug in the AJAX Tagger that caused Wikipedia article links to be incorrect. My apologies!

I'm struggling to understand the purpose and syntax of Lambda Expressions in C# 3.0. They seem convoluted and unnecessary, deviating from C#'s object-oriented nature. I agree with Abhinaba's concerns about C# incorporating functional programming features, potentially making the language more complex and less accessible to the average developer.