Hi I must retrieve data from difference servers. First I login like a user during my site after successfull login I must fetch data from different web servers and display. How do i share just one session with multiple servers. How do i do like this?

Initially when i first login it create session and session id saved on temp folder of this server. After I attempt to access another server how do i use current session that already produced after i drenched in. Any body can suggest us a solution?

You will need to use another session handler.

You are able to:

Store it inside a database - get all servers for connecting to that particular same database. First result for "php store session in database"

Another option is to make use of memcached to keep the periods.

The key factor is you should have a shared resource - whether it's a SQL database, memcached, a NoSQL database, etc. that servers can access. After this you use session_set_save_handler to gain access to the shared resource.

Store periods inside a database that is accessible in the whole server pool.

In complement to any or all these solutions:

Should you store periods in databases, make sure that garbage collecting of periods in PHP is actually triggered (it isn't the situation on Debian-like distrcibutions, they made the decision to garbage periods using their own cron and changed the php.ini to ensure that he never launch any gc, check the session.gc_probability and session.gc_divisor). The primary problem of sessionstorage in databas eis this mean lots of write queries and lots of conflicting access within the database. This can be a good way of worrying a database server like MySQL. So IMHO using another option would be better, this prevents your read/write ratio inside a better web-database way.

You might keep your file storage system and just share the file directory between servers with NFS. Affect the session.save_path setting to make use of something apart from /tmp.

When the only factor you have to share between your server is authentification, then rather than discussing the actual session storage you can share authentification qualifications. Such as the OpenId system in SO, it's what we should call an SSO, for that web part there are several solutions, from OpenId to CAS, yet others. When the information is merged around the client side (ajax, ESI-gate) then you don't actually need a typical session data storage on server-side. This can avoid getting 3 of the 5 influenced web application writing data within the shared session in the same time frame. Other session discussing techniques (database, NFS, even memcached) are mainly accustomed to share your computer data between several servers because Load Balancing tools can put your consecutive HTTP request in one server to a different, but when you actually mean parallel gathering of information you need to really study SSO.