UDDI is a directory service where companies can register and search for Web services.
UDDI stands for Universal Description, Discovery and Integration
UDDI is a directory for storing information about web services
UDDI is a directory of web service interfaces described by WSDL
UDDI communicates via SOAP
UDDI is built into the Microsoft .NET platform
Friday, December 18, 2009
What is WSDL?
WSDL is an XML-based language for locating and describing Web services.
WSDL stands for Web Services Description Language
WSDL is based on XML
WSDL is used to describe Web services
WSDL is used to locate Web services
WSDL is a W3C standard
WSDL stands for Web Services Description Language
WSDL is based on XML
WSDL is used to describe Web services
WSDL is used to locate Web services
WSDL is a W3C standard
What is SOAP?
SOAP is an XML-based protocol to let applications exchange information over HTTP.
Or more simple: SOAP is a protocol for accessing a Web Service.
SOAP stands for Simple Object Access Protocol
SOAP is a communication protocol
SOAP is a format for sending messages
SOAP is designed to communicate via Internet
SOAP is platform independent
SOAP is language independent
SOAP is based on XML
SOAP is simple and extensible
SOAP allows you to get around firewalls
SOAP is a W3C standard
Or more simple: SOAP is a protocol for accessing a Web Service.
SOAP stands for Simple Object Access Protocol
SOAP is a communication protocol
SOAP is a format for sending messages
SOAP is designed to communicate via Internet
SOAP is platform independent
SOAP is language independent
SOAP is based on XML
SOAP is simple and extensible
SOAP allows you to get around firewalls
SOAP is a W3C standard
AJAX Define :
AJAX = Asynchronous JavaScript and XML
AJAX is not a new programming language, but a new technique for creating better, faster, and more interactive web applications.
With AJAX, a JavaScript can communicate directly with the server, with the XMLHttpRequest object. With this object, a JavaScript can trade data with a web server, without reloading the page.
AJAX uses asynchronous data transfer (HTTP requests) between the browser and the web server, allowing web pages to request small bits of information from the server instead of whole pages.
The AJAX technique makes Internet applications smaller, faster and more user-friendly.
AJAX is based on Internet standards
AJAX is based on the following web standards:
JavaScript
XML
HTML
CSS
AJAX applications are browser- and platform-independent.
AJAX is about better Internet-applications
Internet-applications have many benefits over desktop applications; they can reach a larger audience, they are easier to install and support, and easier to develop.
However, Internet-applications are not always as "rich" and user-friendly as traditional desktop applications.
With AJAX, Internet applications can be made richer and more user-friendly
AJAX is not a new programming language, but a new technique for creating better, faster, and more interactive web applications.
With AJAX, a JavaScript can communicate directly with the server, with the XMLHttpRequest object. With this object, a JavaScript can trade data with a web server, without reloading the page.
AJAX uses asynchronous data transfer (HTTP requests) between the browser and the web server, allowing web pages to request small bits of information from the server instead of whole pages.
The AJAX technique makes Internet applications smaller, faster and more user-friendly.
AJAX is based on Internet standards
AJAX is based on the following web standards:
JavaScript
XML
HTML
CSS
AJAX applications are browser- and platform-independent.
AJAX is about better Internet-applications
Internet-applications have many benefits over desktop applications; they can reach a larger audience, they are easier to install and support, and easier to develop.
However, Internet-applications are not always as "rich" and user-friendly as traditional desktop applications.
With AJAX, Internet applications can be made richer and more user-friendly
Wednesday, December 16, 2009
Basic WCF Concept and Terminologies
Windows Communication Foundation was official released with .NET 3.0 a couple of months ago. For those people who're doing connected, distributed systems or are in any way interested in communication aspects of systems, this ought to be a God-send. WCF basically rolled all the different Microsoft messaging formats into one, making it extremely easy to architect the communication layer of simple to complex applications. This tutorial aims to explain the basic concepts behind the common terminology used in WCF development and design.
WCF Programs
WCF programs are basically divided into 3 different types of programs. They are common known as
Clients
Clients are program that consumes the services, they are normally the ones that initiate the messenging to the service. Depending on the designed architecture of your application, it is possible that a service behaves as a client as well.
Services
Services are the programs that offers the services to the consumers. They are the ones that react and process the messages, similar to the backend of the application. They can be viewed as the equivalence of web services in .Net 2.0.
All services have to have endpoints specified in order to work. A good way to remember proper endpoint configurations is ABC. A being Address, B being Binding and C being Contracts.
Address
Address are the expose points of services. Services have to tell the world that where they are via addresses.
Bindings
Bindings will describe to the world on how they will communicate with the world. They contain information such as transport way, how they are encoded, are they reliable etc.
Contracts are of (but not necessary all have to be present) 3 different kinds
Service Contract
Describes what the service does.
Data Contract
Define custom messaging structure.
Message Contract
Define the message format that is passed between services.
Intermediaries
Intermediaries are programs that act as "middle-man", their basic roles can be similar to providing a firewall, routing, gateway etc. They are commonly invisible to the client and services.
Messages
All services and clients communicate via messages, which are made up of one body, and one or more header. All WCF messages are XML formatted and transport neutral. In other words, you can specify different forms of transport (HTTP, MSMQ, Named Pipes etc) for different messages. Within each application, you can specify different messaging transport depending on the communication needs of the system. Basically, messages can be divided into
Simplex
One way messaging. Simplex in short means "fire and forget"
Duplex
Asynchronous two-way messaging. In short this means that once fired, the application will carry on doing its own thing. Upon the return results, it will then handle it.
Request Reply
Synchronous 2 way messaging. This is the common communicate method whereby you'll fire a request, and wait for the response before continuing.
Channels
Before a client and service can talk to each other, they have to go through a channel. Imagine a channel as a pipe, with one end being the input message and the other end with the results of the message. There're different channels that can be stacked onto each other, they are commonly known as Channel Stacks. They can be of these different types:
Reliable Sessions
TCP Transport
Binary Message Encoder
Windows Security
Request Reply
The way in which messages are sent through the pipe (Channel) is known as a Transport and they way at which they are encoded are known as Encodings. Transport can be made up of the following:
HTTP
TCP
MSMQ
Named Pipes
WCF Programs
WCF programs are basically divided into 3 different types of programs. They are common known as
Clients
Clients are program that consumes the services, they are normally the ones that initiate the messenging to the service. Depending on the designed architecture of your application, it is possible that a service behaves as a client as well.
Services
Services are the programs that offers the services to the consumers. They are the ones that react and process the messages, similar to the backend of the application. They can be viewed as the equivalence of web services in .Net 2.0.
All services have to have endpoints specified in order to work. A good way to remember proper endpoint configurations is ABC. A being Address, B being Binding and C being Contracts.
Address
Address are the expose points of services. Services have to tell the world that where they are via addresses.
Bindings
Bindings will describe to the world on how they will communicate with the world. They contain information such as transport way, how they are encoded, are they reliable etc.
Contracts are of (but not necessary all have to be present) 3 different kinds
Service Contract
Describes what the service does.
Data Contract
Define custom messaging structure.
Message Contract
Define the message format that is passed between services.
Intermediaries
Intermediaries are programs that act as "middle-man", their basic roles can be similar to providing a firewall, routing, gateway etc. They are commonly invisible to the client and services.
Messages
All services and clients communicate via messages, which are made up of one body, and one or more header. All WCF messages are XML formatted and transport neutral. In other words, you can specify different forms of transport (HTTP, MSMQ, Named Pipes etc) for different messages. Within each application, you can specify different messaging transport depending on the communication needs of the system. Basically, messages can be divided into
Simplex
One way messaging. Simplex in short means "fire and forget"
Duplex
Asynchronous two-way messaging. In short this means that once fired, the application will carry on doing its own thing. Upon the return results, it will then handle it.
Request Reply
Synchronous 2 way messaging. This is the common communicate method whereby you'll fire a request, and wait for the response before continuing.
Channels
Before a client and service can talk to each other, they have to go through a channel. Imagine a channel as a pipe, with one end being the input message and the other end with the results of the message. There're different channels that can be stacked onto each other, they are commonly known as Channel Stacks. They can be of these different types:
Reliable Sessions
TCP Transport
Binary Message Encoder
Windows Security
Request Reply
The way in which messages are sent through the pipe (Channel) is known as a Transport and they way at which they are encoded are known as Encodings. Transport can be made up of the following:
HTTP
TCP
MSMQ
Named Pipes
Friday, December 11, 2009
Tamil Site :
http://www.tamilcomputer.ch
http://kanimozhi.org.in
http://www.thamilworld.com/forum/lofiversion/index.php?f21.html
http://tamilelibrary.org/ - ல் -
Tamil Fonts, Softwares, Interconversion of files, Tamil webpages தலைப்பின் கீழ் பாருங்கள், பயன் அளிக்கலாம்
http://kanimozhi.org.in
http://www.thamilworld.com/forum/lofiversion/index.php?f21.html
http://tamilelibrary.org/ - ல் -
Tamil Fonts, Softwares, Interconversion of files, Tamil webpages தலைப்பின் கீழ் பாருங்கள், பயன் அளிக்கலாம்
Friday, November 6, 2009
Different between dot net 3.5/3.0/2.0 :
The following are the differences between 3.5 ,3.0 and 2.0
.net 3.0 is mainly used for windows development.
.net 3.5 is multi targeted - from dropdown to build the application in .net 3.0/3.5/2.0.
All 3 frameworks used the same CLR of 2.0 but new features implemented to support the dlinq or linq features.
.net 3.5 has good Designer experience, JavaScript debugging and IntelliSense features, and the ability to view and even step into the core .NET Framework code during debugging.
I would like to mention certain feature that was introduced in 2.0
- Generics
- Partial Class
- Membership Providers
- ADO.NET
to list a few.
With 3.5 we have a new set of framework to work with
- WCF
- WPF
- Windows WF
- LINQ
- ASP.NET AJAX
to list a few.
To be more precise we can simply say
framework 3.0 = 2.0 + (WCF/WPF/WF/LINQ)
So this means that the web based capabilities have been enhanced.
ASP.NET 3.5 Features.
1. Nested Master Pages.
2. Datapager Control.
3. Listview Control.
4.Silverlight.
5. Ajax
Net Framework 3.5 can have Some of New Fetures(c#)
1.Linq to Sql (liq to sql,linq to dataset,linq to xml,linq to entities,linq to objects etc)
2.Lambda Expression.
3.Annoymous Types.
4.Extenction Methods.
5.Paritial Methods.
6.Local type Varibles.
Asp.net
1.Datapager Control.
2.Listview Control
3.Ajax toolkit
ASP.NET 3.5 are detailed here: http://www.asp.net/downloads/vs2008/
.net 3.0 is mainly used for windows development.
.net 3.5 is multi targeted - from dropdown to build the application in .net 3.0/3.5/2.0.
All 3 frameworks used the same CLR of 2.0 but new features implemented to support the dlinq or linq features.
.net 3.5 has good Designer experience, JavaScript debugging and IntelliSense features, and the ability to view and even step into the core .NET Framework code during debugging.
I would like to mention certain feature that was introduced in 2.0
- Generics
- Partial Class
- Membership Providers
- ADO.NET
to list a few.
With 3.5 we have a new set of framework to work with
- WCF
- WPF
- Windows WF
- LINQ
- ASP.NET AJAX
to list a few.
To be more precise we can simply say
framework 3.0 = 2.0 + (WCF/WPF/WF/LINQ)
So this means that the web based capabilities have been enhanced.
ASP.NET 3.5 Features.
1. Nested Master Pages.
2. Datapager Control.
3. Listview Control.
4.Silverlight.
5. Ajax
Net Framework 3.5 can have Some of New Fetures(c#)
1.Linq to Sql (liq to sql,linq to dataset,linq to xml,linq to entities,linq to objects etc)
2.Lambda Expression.
3.Annoymous Types.
4.Extenction Methods.
5.Paritial Methods.
6.Local type Varibles.
Asp.net
1.Datapager Control.
2.Listview Control
3.Ajax toolkit
ASP.NET 3.5 are detailed here: http://www.asp.net/downloads/vs2008/
