A session is a series of interactions between two communication end points that occur during the span of a single connection. Typically, one end point requests a connection with another specified end point and if that end point replies agreeing to the connection, the end points take turns exchanging commands and data ("talking to each other"). The session begins when the connection is established at both ends and terminates when the connection is ended.

In the standard industry communications reference model, Open Systems Interconnection (OSI), the Session layer (sometimes called the "port layer") manages the setting up and taking down of the association between two communicating end points that is called a connection. A connection is maintained while the two end points are communicating back and forth in a conversation or session of some duration.

For Internet applications, each session is related to a particular port, a number that is associated with a particular upper layer application. For example, the HTTP program or daemon always has port number 80. The port numbers associated with the main Internet applications are referred to as well-known port numbers.

The basic categories are given below-
1. Using Cookies
2. Using Session API in Servlets
3. Using Hidden form fields
4. URL Rewriting

Answered by Yash , an ibibo Master, at 10:14 AM on July 03, 2008

A session is a series of interactions between two communication end points that occur during the span of a single connection. Typically, one end point requests a connection with another specified end point and if that end point replies agreeing to the connection, the end points take turns exchanging commands and data ("talking to each other"). The session begins when the connection is established at both ends and terminates when the connection is ended.

In the standard industry communications reference model, Open Systems Interconnection (OSI), the Session layer (sometimes called the "port layer") manages the setting up and taking down of the association between two communicating end points that is called a connection. A connection is maintained while the two end points are communicating back and forth in a conversation or session of some duration.

For Internet applications, each session is related to a particular port, a number that is associated with a particular upper layer application. For example, the HTTP program or daemon always has port number 80. The port numbers associated with the main Internet applications are referred to as well-known port numbers.

The basic categories are given below-
1. Using Cookies
2. Using Session API in Servlets
3. Using Hidden form fields
4. URL Rewriting

Answered by Shobhit , an ibibo Master, at 6:04 PM on June 25, 2008

A session is a series of interactions between two communication end points that occur during the span of a single connection. Typically, one end point requests a connection with another specified end point and if that end point replies agreeing to the connection, the end points take turns exchanging commands and data ("talking to each other"). The session begins when the connection is established at both ends and terminates when the connection is ended.

In the standard industry communications reference model, Open Systems Interconnection (OSI), the Session layer (sometimes called the "port layer") manages the setting up and taking down of the association between two communicating end points that is called a connection. A connection is maintained while the two end points are communicating back and forth in a conversation or session of some duration.

For Internet applications, each session is related to a particular port, a number that is associated with a particular upper layer application. For example, the HTTP program or daemon always has port number 80. The port numbers associated with the main Internet applications are referred to as well-known port numbers.

The basic categories are given below-
1. Using Cookies
2. Using Session API in Servlets
3. Using Hidden form fields
4. URL Rewriting

Answered by Madhurima , an ibibo Master, at 1:40 PM on June 13, 2008

Hi there

A session is a series of interactions between two communication end points that occur during the span of a single connection. Typically, one end point requests a connection with another specified end point and if that end point replies agreeing to the connection, the end points take turns exchanging commands and data ("talking to each other"). The session begins when the connection is established at both ends and terminates when the connection is ended.

In the standard industry communications reference model, Open Systems Interconnection (OSI), the Session layer (sometimes called the "port layer") manages the setting up and taking down of the association between two communicating end points that is called a connection. A connection is maintained while the two end points are communicating back and forth in a conversation or session of some duration.

For Internet applications, each session is related to a particular port, a number that is associated with a particular upper layer application. For example, the HTTP program or daemon always has port number 80. The port numbers associated with the main Internet applications are referred to as well-known port numbers.

The basic categories are given below-
1. Using Cookies
2. Using Session API in Servlets
3. Using Hidden form fields
4. URL Rewriting

Answered by Reeta K , an ibibo Master, at 1:05 PM on June 09, 2008

well marven, Session class represents a mail session and is not subclassed. It collects together properties and defaults used by the mail API's. A single default session can be shared by multiple applications on the desktop. Unshared sessions can also be created.

The Session class provides access to the protocol providers that implement the Store, Transport, and related classes. The protocol providers are configured using the following files:

* javamail.providers and javamail.default.providers
* javamail.address.map and javamail.default.address.map

Eac h javamail.X resource file is searched for using three methods in the following order:

1. java.home/lib/javamail.X
2. META-INF/javamail.X
3. META-INF/javamail.default.X

The first method allows the user to include their own version of the resource file by placing it in the lib directory where the java.home property points. The second method allows an application that uses the JavaMail APIs to include their own resource files in their application's or jar file's META-INF directory. The javamail.default.X default files are part of the JavaMail mail.jar file.
For more details , Please visit the source site :

http://java.sun.com/j2ee/ 1.4/d ocs/api/javax/mail/Session.htm l

Answered by satyaiitk , an ibibo Master, at 11:42 AM on June 07, 2008

a session is a semi-permanent interactive information exchange, also known as a dialogue, a conversation or a meeting, between two or more communicating devices, or between a computer and user (see Login session). A session is set up or established at a certain point in time, and torn down at a later point in time. An established communication session may involve more than one message in each direction. A session is typically, but not always, stateful, meaning that at least one of the communicating parts need to save information about the session history in order to be able to communicate, as opposed to stateless communication, where the communication consists of independent requests with responses.

Communication sessions may be implemented as part of protocols and services at the application layer, at the session layer or at the transport layer in the OSI model.

* Application layer examples:
o HTTP sessions, which may allow dynamic web pages, i.e. interactive web pages, as opposed to static web pages.
o A telnet remote login session
* Session layer example:
o A Session Initiation Protocol (SIP) based Internet phone call
* Transport layer example:
o A TCP session, which is synonymous to a TCP virtual circuit, a TCP connection, or an established TCP socket.

Session support in PHP consists of a way to preserve certain data across subsequent accesses. This enables you to build more customized applications and increase the appeal of your web site.

Answered by Radhe Radhe , an ibibo Advisor, at 6:39 PM on June 06, 2008

well marven, The Session class represents a mail session and is not subclassed. It collects together properties and defaults used by the mail API's. A single default session can be shared by multiple applications on the desktop. Unshared sessions can also be created.

The Session class provides access to the protocol providers that implement the Store, Transport, and related classes. The protocol providers are configured using the following files:

* javamail.providers and javamail.default.providers
* javamail.address.map and javamail.default.address.map

Eac h javamail.X resource file is searched for using three methods in the following order:

1. java.home/lib/javamail.X
2. META-INF/javamail.X
3. META-INF/javamail.default.X

The first method allows the user to include their own version of the resource file by placing it in the lib directory where the java.home property points. The second method allows an application that uses the JavaMail APIs to include their own resource files in their application's or jar file's META-INF directory. The javamail.default.X default files are part of the JavaMail mail.jar file.

File location depends upon how the ClassLoader method getResource is implemented. Usually, the getResource method searches through CLASSPATH until it finds the requested file and then stops. JDK 1.1 has a limitation that the number of files of each name that will be found in the CLASSPATH is limited to one. However, this only affects method two, above; method one is loaded from a specific location (if allowed by the SecurityManager) and method three uses a different name to ensure that the default resource file is always loaded successfully. J2SE 1.2 and later are not limited to one file of a given name.

The ordering of entries in the resource files matters. If multiple entries exist, the first entries take precedence over the later entries. For example, the first IMAP provider found will be set as the default IMAP implementation until explicitly changed by the application. The user- or system-supplied resource files augment, they do not override, the default files included with the JavaMail APIs. This means that all entries in all files loaded will be available.

For more details , Please visit the source site :

http://java.sun.com/j2ee/ 1.4/d ocs/api/javax/mail/Session.htm l

Answered by Romi , an ibibo Master, at 6:37 PM on June 06, 2008

A session is a series of interactions between two communication end points that occur during the span of a single connection. Typically, one end point requests a connection with another specified end point and if that end point replies agreeing to the connection, the end points take turns exchanging commands and data ("talking to each other"). The session begins when the connection is established at both ends and terminates when the connection is ended.

In the standard industry communications reference model, Open Systems Interconnection (OSI), the Session layer (sometimes called the "port layer") manages the setting up and taking down of the association between two communicating end points that is called a connection. A connection is maintained while the two end points are communicating back and forth in a conversation or session of some duration.

For Internet applications, each session is related to a particular port, a number that is associated with a particular upper layer application. For example, the HTTP program or daemon always has port number 80. The port numbers associated with the main Internet applications are referred to as well-known port numbers.

The basic categories are given below-
1. Using Cookies
2. Using Session API in Servlets
3. Using Hidden form fields
4. URL Rewriting

Answered by Nagendra , an ibibo Master, at 6:19 PM on June 06, 2008

a session is a semi-permanent interactive information exchange, also known as a dialogue, a conversation or a meeting, between two or more communicating devices, or between a computer and user (see Login session). A session is set up or established at a certain point in time, and torn down at a later point in time. An established communication session may involve more than one message in each direction. A session is typically, but not always, stateful, meaning that at least one of the communicating parts need to save information about the session history in order to be able to communicate, as opposed to stateless communication, where the communication consists of independent requests with responses.

Communication sessions may be implemented as part of protocols and services at the application layer, at the session layer or at the transport layer in the OSI model.

* Application layer examples:
o HTTP sessions, which may allow dynamic web pages, i.e. interactive web pages, as opposed to static web pages.
o A telnet remote login session
* Session layer example:
o A Session Initiation Protocol (SIP) based Internet phone call
* Transport layer example:
o A TCP session, which is synonymous to a TCP virtual circuit, a TCP connection, or an established TCP socket.

Session support in PHP consists of a way to preserve certain data across subsequent accesses. This enables you to build more customized applications and increase the appeal of your web site.

A visitor accessing your web site is assigned a unique id, the so-called session id. This is either stored in a cookie on the user side or is propagated in the URL.

The session support allows you to register arbitrary numbers of variables to be preserved across requests. When a visitor accesses your site, PHP will check automatically (if session.auto_start is set to 1) or on your request (explicitly through session_start() or implicitly through session_register()) whether a specific session id has been sent with the request. If this is the case, the prior saved environment is recreated.

Answered by Om Prakash , an ibibo Master, at 6:12 PM on June 06, 2008

well , I am feeling HAPPY to answer your question , I would like to suggest you to access the source site if it's available , for more information.

A session is set up or established at a certain point in time, and torn down at a later point in time. An established communication session may involve more than one message in each direction. A session is typically, but not always, stateful, meaning that at least one of the communicating parts need to save information about the session history in order to be able to communicate, as opposed to stateless communication, where the communication consists of independent requests with responses.
TCP sessions are typically implemented in software using child processes and/or multithreading, where a new process or thread is created when the computer establishes or joins a session. HTTP sessions are typically not implemented using one thread per session, but by means of a database with information about the state of each session. The advantage with multiple processes or threads is relaxed complexity of the software, since each thread is an instance with its own history and encapsulated variables. The disadvantage is large overhead in terms of system resources, and that the session may be interrupted if the system is restarted.

When a client may connect to any in a cluster of servers, a special problem is encountered in maintaining consistency when the servers must maintain session state. The client must either be directed to the same server for the duration of the session, or the servers must transmit server-side session information via a shared file system or database. Otherwise, the client may reconnect to a different server than the one it started the session with, which will cause problems when the new server does not have access to the stored state of the old one.
Server-side sessions are handy and efficient, but can become difficult to handle in conjunction with load-balancing/high-availabili ty systems and are not usable at all in embedded systems with no storage

Hope it will help you out.

Answered by Uttam , an ibibo Master, at 2:13 PM on June 06, 2008