Posts

Showing posts from December, 2007

Service Oriented Architecture

Image
  The goal for a SOA is a world wide mesh of collaborating services, which are published and available for invocation on the Service Bus. Adopting SOA is essential to deliver the business agility and IT flexibility promised by Web Services. These benefits are delivered not by just viewing service architecture from a technology perspective and the adoption of Web Service protocols, but require the creation of a Service Oriented Environment that is based on the following key principals: Service is the important concept. Web Services are the set of protocols by which Services can be published, discovered and used in a technology neutral, standard form. SOA is not just an architecture of services seen from a technology perspective, but the policies, practices, and frameworks by which we ensure the right services are provided and consumed. With SOA it is critical to implement processes that ensure that there are at least two different and separate processes—for provider and cons

SVG & Mobile

Image
Posted November 30th, 2007 by ronan http://dev.mobi/node/704 It has always surprised me that the mobile industry has not made better use of SVG. On the face of it, SVG is perfectly suited to publishing rich content on mobile devices for a number of reasons: It is a compact way of representing vector graphics SVG graphics (in keeping with the name) can be scaled to arbitrary sizes, removing some of issues with screen dimension proliferation on mobile devices It is an open standard Device support is better than you might think (more on this later) Because SVG is based on XML, many existing XML tools can be used to generate content This article summarises the capabilities of SVG and how best to take advantage of it for mobile applications. I will not attempt to describe how to build SVG content since there are plenty of good tutorials elsewhere (see References & Links section below). Description of SVG First a quick recap on what exactly SVG is all about. From the Wik

The problem with InnerHTML

  Published by Julien Lecomte at 6:24 pm under Web Development The innerHTML property is extremely popular because it provides a simple way to completely replace the contents of an HTML element. Another way to do that is to use the DOM Level 2 API ( removeChild , createElement , appendChild ) but using innerHTML is by far the easiest and most efficient way to modify the DOM tree. However, innerHTML has few problems of its own that you need to be aware of: Improper handling of the innerHTML property can enable script-injection attacks on Internet Explorer when the HTML string contains a script tag marked as deffered: <script defer>...<script> Setting innerHTML will destroy existing HTML elements that have event handlers attached to them, potentially creating a memory leak on some browsers. There are a few other minor drawbacks worth mentioning: You don't get back a reference to the element(s) you just created, forcing you to add code to retrieve those

How to Share Session State Between Classic ASP and ASP.NET

Image
How to Share Session State Between Classic ASP and ASP.NET Billy Yuen Microsoft Corporation Summary: Discusses how to share session state between classic ASP and Microsoft ASP.NET using Microsoft .NET Framework classes and the serialization feature of the .NET Framework. Sharing session state allows converting existing ASP applications to ASP.NET applications in stages while running the applications side by side. (12 printed pages) Download the source code for this article . Contents Introduction Conceptual Overview ASP.NET Implementation ASP Implementation Demo Program Incorporating the COM Object in an Existing ASP Application Limitation/Improvement Conclusion Introduction Microsoft® ASP.NET is the latest Microsoft technology for developing Web-based applications. It offers a number of advantages over the classic ASP script technology, including: 1) a better development structure by separating the UI presentation from business logic; 2) its code is fully compiled instead of inte

Prototype Developer Notes

Developer Notes for prototype.js covers version 1.5.0 Table of Contents What is that? Related article The utility functions Using the $() function Using the $$() function Using the $F() function Using the $A() function Using the $H() function Using the $R() function Using the Try.these() function Tricked out strings String substitutions String templates The Ajax object Using the Ajax.Request class Using the Ajax.Updater class What are all those "?" and squares? Enumerating... Wow! Damn! Wahoo! Loops, Ruby-style Your arrays on steroids Books I strongly recommend Reference for prototype.js Extensions to the JavaScript classes Extensions for the Object class Extensions for the Number class Extensions for the Function class Extensions for the String class Extensions for the Array class Extensions for the document DOM object Extensions for the Event object New objects and classes defined by prototyp