Answer Posted / p.sivasankar

1>>mysql_connect() — Open a connection to a MySQL Server

Description:
resource mysql_connect ([ string $server [, string
$username [, string $password [, bool $new_link [, int
$client_flags ]]]]] )
Opens or reuses a connection to a MySQL server

2>>mysql_pconnect — Open a persistent connection to a MySQL
server

Description:
resource mysql_pconnect ([ string $server [, string
$username [, string $password [, int $client_flags ]]]] )

Establishes a persistent connection to a MySQL server.

mysql_pconnect() acts very much like mysql_connect() with
two major differences.

First, when connecting, the function would first try to
find a (persistent) link that's already open with the same
host, username and password. If one is found, an identifier
for it will be returned instead of opening a new
connection.

Second, the connection to the SQL server will not be closed
when the execution of the script ends. Instead, the link
will remain open for future use (mysql_close() will not
close links established by mysql_pconnect()).

This type of link is therefore called 'persistent'

What exactly is PHP?

966

---

Does php class need constructor?

906

---

Is array a key php?

921

---

Why do we use inheritance in php?

1004

---

What is the super method?

966

---

4 down vote favorite share [g+] share [fb] share [tw] I am developing my site using server side sessions using redis as backend for saving the session. Now the issue which is bothering me is of user leaving the website without logging out. I mean user simply closes the browser which causes the cookie to be deleted. Now session of that user still exists on the server and will not be used again as new login requires creating a new session due to security reasons. To avoid the case where hacker steals the old cookie and use it after user login again with same old session id. In essence user leaves the website without explicitly logging out and his session will be deleted after certain time limit of inaccessibility. I am thinking time limit of 30-60 minutes. Also with every new request from user his cookie will also be updated to keep track of when the user last time accessed the site. But nowadays, people let site remain open for long time without accessing it. For example users open facebook and gmail in new tabs and forget about them for 2-3 hours and still they are not asked to login again. Is letting a 2-3 hours old cooke access the session secure? My concern is someone steals user cookie and use it 2-3 hours later. Thinking on this topic has also forced me to question how facebook manages security if user can use a session where they are not accessing it for long periods of time and still they remain logged in. Or is it not secure for me to keep logged in when am not accessing the site session for longer period of time? It can be the case also there is some pinging mechanism using which sites keep track of user having their site open in a browser and when browser closes they are notified and can work accordingly. My website is a social network and needs all those security and usage features which a social network may need. I am new to web security and web development in general and may be the case where my above questions may seem a little basic. If you feel that is the case kindly point to some good reference where I can read and find answers to my question.

2091

---

What is difference between session_unset and session_destroy?

972

---

Are static variables final?

964

---

How can you get web browser’s details using PHP?

926

---

What is difference between rest api and restful api?

928

---

Is php better than java?

937

---

What is the meaning of xdebug?

932

---

What is a stored procedure in mysql?

1042

---

How to process the uploaded files?

1066

---

Is age interval or ordinal data?

936

---