Objective is to keep track of what all I am working on at the moment.
Wednesday, May 18, 2005
Monday, May 16, 2005
Thursday, May 12, 2005
Monday, May 09, 2005
Nontraditional advertising: Vodka brand advertises thru Blogs
Vodka Brand Hopes Drinking and Blogging Mix
Swedish spirits importer Svedka Vodka has launched a lifestyle blog to reach trendsetters and tastemakers. The site, at GardenOfSweden.com, features gritty underground content on sex and erotica, nightlife, movies, literature, travel, gossip, and vodka cocktail recipes
Swedish spirits importer Svedka Vodka has launched a lifestyle blog to reach trendsetters and tastemakers. The site, at GardenOfSweden.com, features gritty underground content on sex and erotica, nightlife, movies, literature, travel, gossip, and vodka cocktail recipes
Tuesday, May 03, 2005
Wednesday, April 27, 2005
8 Mn + VoIP home users
CXOtoday.com > News > Business > Linksys To Expand VoIP Presence With Sipura Acquisition: "Synergy Research Group reports that today there are close to 8 million home users worldwide using VoIP to make phone calls over their broadband connections. By 2009, Synergy anticipates this number to grow to 58.9 million home users using VoIP to talk to friends and family around the world using broadband and VoIP technology. "
Choosing the right level of granularity in SOA
IBM WebSphere Developer Technical Journal: Web Services Architectures and Best Practices
Check the contents and click on appropriate link
Check the contents and click on appropriate link
SLAng: A language to define QoS
Click here
Application or web services are increasingly being used
across organisational boundaries. Moreover, new services
are being introduced at the network and storage level. Languages
to specify interfaces for such services have been researched
and transferred into industrial practice. We investigate
end-to-end quality of service (QoS) and highlight
that QoS provision has multiple facets and requires complex
agreements between network services, storage services
and middleware services. We introduce SLAng, a language
for defining Service Level Agreements (SLAs) that accommodates
these needs. We illustrate how SLAng is used to
specify QoS in a case study that uses a web services speci-
fication to support the processing of images across multiple
domains and we evaluate our language based on it.
Application or web services are increasingly being used
across organisational boundaries. Moreover, new services
are being introduced at the network and storage level. Languages
to specify interfaces for such services have been researched
and transferred into industrial practice. We investigate
end-to-end quality of service (QoS) and highlight
that QoS provision has multiple facets and requires complex
agreements between network services, storage services
and middleware services. We introduce SLAng, a language
for defining Service Level Agreements (SLAs) that accommodates
these needs. We illustrate how SLAng is used to
specify QoS in a case study that uses a web services speci-
fication to support the processing of images across multiple
domains and we evaluate our language based on it.
Quality of Service in Service-Oriented Architectures
Quality of Service in Service-Oriented Architectures
It is noted that there are two ways in which the term Quality of Service (QoS) is commonly used: firstly in its traditional distributed multimedia sense, which relates almost entirely to network performance, and secondly in its service-centric sense which refers to a wider range of non-functional service characteristics. In this paper the complexity of enabling this latter QoS definition in service-centric systems is discussed. A survey of existing technologies which are applicable in this area is undertaken, concentrating on QoS specification. From this survey it is concluded that there are a number of areas in which these technologies lack, or that remain open for research. In particular, the following needs are identified: a general purpose QoS specification language; a QoS-based service discovery mechanism to complement UDDI; a system for Service Level Agreement (SLA) negotiation, which should work with specifications in the aforementioned language; and systems for QoS measurement and monitoring. Research into using underlying technologies to provide QoS in service-centric systems and into mapping from SLA specifications to configuration of such technologies is also identified as key
It is noted that there are two ways in which the term Quality of Service (QoS) is commonly used: firstly in its traditional distributed multimedia sense, which relates almost entirely to network performance, and secondly in its service-centric sense which refers to a wider range of non-functional service characteristics. In this paper the complexity of enabling this latter QoS definition in service-centric systems is discussed. A survey of existing technologies which are applicable in this area is undertaken, concentrating on QoS specification. From this survey it is concluded that there are a number of areas in which these technologies lack, or that remain open for research. In particular, the following needs are identified: a general purpose QoS specification language; a QoS-based service discovery mechanism to complement UDDI; a system for Service Level Agreement (SLA) negotiation, which should work with specifications in the aforementioned language; and systems for QoS measurement and monitoring. Research into using underlying technologies to provide QoS in service-centric systems and into mapping from SLA specifications to configuration of such technologies is also identified as key
Using Service-Oriented Architecture and Component-Based Development to Build Web Service Applications
Building an enterprise-scale software system is a complex undertaking. Despite decades of technological advances, the demands imposed by today’s information systems frequently stretch to breaking point a company’s ability to design, construct, and evolve its mission-critical software solutions. In particular, few new systems are designed from the ground up. Rather, a software architect’s task is commonly that of extending the life of an existing solution by describing new business logic that manipulates an existing repository of data, presenting existing data and transactions through new channels such as an Internet browser or handheld devices, integrating previously disconnected systems supporting overlapping business activities, and so on. To assist software developers, commercial software infrastructure products are now available from vendors such as Microsoft and IBM. They form the centerpiece of the approaches to software development they advocate in their .NET and WebSphere product lines, respectively. Both approaches focus on assembly of hsystems from distributed services. However, is there anything new about building enterprise-scale solutions from services? How do the lessons of component-based systems apply to construction of service-based architectures (SOA)? What are the best approaches for building high quality systems for deployment to this new generation of software infrastructure products? These important questions are the topic of this paper
Click here
Contents.........................................................................................................................................................2 Introduction...................................................................................................................................................2
What Is a Service-Oriented Architecture?......................................................................................................3
Interface-Based Design.............................................................................................................................5
Interface Behavior.................................................................................................................................5
Architecting Service-Oriented Systems..........................................................................................................6
Layering Application Design..................................................................................................................6
Example Customer Model......................................................................................................................7
A Component-Based Design......................................................................................................................8
A Service-Oriented Design.........................................................................................................................8
Caching in Service Oriented Design.......................................................................................................9
XML Web Services Application Design......................................................................................................10
Web Service Design and Implementation Patterns...................................................................................11
Performance and Reliability.................................................................................................................11
Scalability Through Asynchronous Behavior and Queuing.................................................................12
Information Leasing Revisited.............................................................................................................13
Resulting Web Service Design Model......................................................................................................14
Click here
Contents.........................................................................................................................................................2 Introduction...................................................................................................................................................2
What Is a Service-Oriented Architecture?......................................................................................................3
Interface-Based Design.............................................................................................................................5
Interface Behavior.................................................................................................................................5
Architecting Service-Oriented Systems..........................................................................................................6
Layering Application Design..................................................................................................................6
Example Customer Model......................................................................................................................7
A Component-Based Design......................................................................................................................8
A Service-Oriented Design.........................................................................................................................8
Caching in Service Oriented Design.......................................................................................................9
XML Web Services Application Design......................................................................................................10
Web Service Design and Implementation Patterns...................................................................................11
Performance and Reliability.................................................................................................................11
Scalability Through Asynchronous Behavior and Queuing.................................................................12
Information Leasing Revisited.............................................................................................................13
Resulting Web Service Design Model......................................................................................................14
Monday, April 25, 2005
ColorCombos.com - Web Color Combinations Tool and Library
Welcome to ColorCombos.com. This site was built to help web developers quickly select and test color combinations.
The heart of the site is the Combo Tester, which allows web developers to see how different color combinations work together on the screen.
If you are looking for Color Combination ideas, check out the Combo Library.
ColorCombos.com - Web Color Combinations Tool and Library
The heart of the site is the Combo Tester, which allows web developers to see how different color combinations work together on the screen.
If you are looking for Color Combination ideas, check out the Combo Library.
ColorCombos.com - Web Color Combinations Tool and Library
Site for Web Color combos
I wish we had found this site earlier. Anyways we can use this in future
:)
Regards
HimS
Date: Sun, 24 Apr 2005 14:39:14 +0530
From: Manoj Vijayan
Subject: Site for web color combos
Welcome to ColorCombos.com. This site was built to help web developers
quickly select and test color combinations.
The heart of the site is the Combo Tester, which allows web developers
to see how different color combinations work together on the screen.
If you are looking for Color Combination ideas, check out the Combo
Library.
www.ColorCombos.com
21 Rules of Thumb: How Microsoft develops its Software
Jim McCarthy's 21 Rules of shipping great software on time:David Gristwood's WebLog : 21 Rules of Thumb � How Microsoft develops its Software
Tuesday, April 12, 2005
Monday, February 28, 2005
IBM Emerging Technologies Toolkit FAQ
IBM Emerging Technologies Toolkit: talks about web services etc. The tool kit by IBM provides the basic software components needed to design, develop, and execute emerging autonomic, web services, and grid-related technologies.
Friday, January 28, 2005
E-Mail Bounce Management
E-Mail Bounce Management is the requirement of the industry. Especially our customers whose email campaign volumes reaches thousands of electronic communications per day.
Bounced emails, have the potential of not only putting the system out of gear, but also increases the email costs for the user (Hosting charges per mail box fee with a constraint of how many emails you can recieve and send)
Hence we should strive to handle this OOTB.
Bounced emails, have the potential of not only putting the system out of gear, but also increases the email costs for the user (Hosting charges per mail box fee with a constraint of how many emails you can recieve and send)
Hence we should strive to handle this OOTB.
Tuesday, January 04, 2005
Marketing ideas
What is the goal of a company? To make money for its owners.
How to make money? By selling products
How to make more money? By selling more products
What if the market does not buy more product? Redefine the market by either investing in engg to make develop more products or by repackaging the existing product such that the benefit offered by the packaging outweighs the existing products in the same market.
Well Apple seems to be doing exactly that by coming out with a headless mac. They are trying to address the complaint that Apple is unaffordable. At $499, it is definitely affordable.
How to make money? By selling products
How to make more money? By selling more products
What if the market does not buy more product? Redefine the market by either investing in engg to make develop more products or by repackaging the existing product such that the benefit offered by the packaging outweighs the existing products in the same market.
Well Apple seems to be doing exactly that by coming out with a headless mac. They are trying to address the complaint that Apple is unaffordable. At $499, it is definitely affordable.
Subscribe to:
Posts (Atom)