-----------------------------------------------------------

New Message on BDOTNET

-----------------------------------------------------------
From: Ravi_Kumar_Bits
Message 2 in Discussion



Hi,



Q1. When we use validation controls
they will be triggered not only at the client side but also at the server
side, this action is by default.

        So
all the validation controls will be fired once again at the server.This
you dont need to do once again.

Q2. Mainly we go for SQL Server when
we our deployment mode is Web Garden or Web Farm and mainly when we want
reliablity in our              
  transactions. But you can ask me why cant we use State Server
for that reason, if state server gets crashed all the session    
            information is
lost, but in case of SQL Server there is always the case of recovery.

        Adv
: Reliablity

        DisAdv
: Slow in Performance

Q3. Session is the data that is stored
in the server side, and is created on Per-user basis.But in the case of
Cookies normally these are            
    stored at the client side.Here i will give small
description like what is the relation between cookies and session

        The
first time a user requests an .aspx file within a given application, ASPNET_WP
(worker process) generates a SessionID. A          
      number produced by a complex algorithm, the
SessionID uniquely identifies each user's session. At the beginning of
a new session,         the server stores the
Session ID in the user's Web browser as a cookie.



        The
SessionID cookie is similar to a locker key in that, as the user interacts
with an application during a session, ASP can store information  
      for the user in a "locker" on the
server. The user's SessionID cookie, transmitted in the HTTP request header,
enables access to this            
    information in the way that a locker key enables
access to a locker's contents. Each time that ASP receives a request for
a page, it checks         the HTTP request
header for a SessionID cookie.

        

        After
storing the SessionID cookie in the user's browser, ASPWP reuses the same
cookie to track the session, even if the user requests      
          another .aspx file,
or requests an .aspx file running in other application. Likewise, if the
user deliberately abandons or lets the session        
        timeout, and then proceeds
to request another .aspx file, ASPWP begins a new session using the same
cookie. The only time a user          
      receives a new SessionID cookie is when the
server administrator restarts the server, thus clearing the SessionID settings
stored in                
memory, or the user restarts the Web browser.

        

Q4. Method1. If you want paging in data
grid Use SqlDataAdapter class fill the dataset bind the dataset to grid

      Method2. If you
do not want paging and for good performance use SqlDataReader class and
bind the dataset to grid            
    



Have a nice day



Regards

Ravi Kumar . P










"Mamatha_md"
<[EMAIL PROTECTED]> 

06/23/2004 09:39 AM





Please respond to

"BDOTNET" <[EMAIL PROTECTED]>






To
"BDOTNET" <[EMAIL PROTECTED]>


cc



Subject
Query

















New Message on BDOTNET





Query





Reply





 
Reply
to Sender   Recommend


Message 1 in Discussion







From: Mamatha_md




Hi,

 

Can i get the answers for the following
Q's?

 

1. When i use the validation controls,
they will be triggered at the client side. How do i make it execute at
server side?

2. What are the advantages and disadvantage of storing the session values
in SQL server?

3. What is the difference between cookies and session variables?

4. What are the different methods available to bind the grid with data?

 

Regards,

Mamatha





View
other groups in this category. 






Also on MSN:

Start
Chatting |
Listen
to Music |
House
& Home |
Try
Online Dating |
Daily
Horoscopes 









To stop getting this e-mail, or change how often it arrives, go to your
E-mail
Settings. 



Need help? If you've forgotten your password, please go to Passport
Member Services. 

For other questions or feedback, go to our Contact
Us page. 



If you do not want to receive future e-mail from this MSN group, or if
you received this message by mistake, please click the "Remove"
link below. On the pre-addressed e-mail message that opens, simply click
"Send". Your e-mail address will be deleted from this group's
mailing list. 

Remove
my e-mail address from BDOTNET.




ForwardSourceID:NT0000D7E6
   



-----------------------------------------------------------

To stop getting this e-mail, or change how often it arrives, go to your E-mail 
Settings.
http://groups.msn.com/bdotnet/_emailsettings.msnw

Need help? If you've forgotten your password, please go to Passport Member Services.
http://groups.msn.com/_passportredir.msnw?ppmprop=help

For other questions or feedback, go to our Contact Us page.
http://groups.msn.com/contact

If you do not want to receive future e-mail from this MSN group, or if you received 
this message by mistake, please click the "Remove" link below. On the pre-addressed 
e-mail message that opens, simply click "Send". Your e-mail address will be deleted 
from this group's mailing list.
mailto:[EMAIL PROTECTED]

Reply via email to