With every request to server , no need to send data in web storage to server

can u tell me  max by when can they reply to my question


My question was :how communication with server is done  , when application is developed using web storage , state maintainence at server how is done , because cookies where used to maintain state , if now no cookie then how the state will be maintained at server.


Because any way we are using HTTP protocol in both case , so to make it state full , what need to be done at server , to identify user that , i m the same user who has already logged in


... i need the answer of this question in detail

pls 

I have forwarded this thread to many of our experts... Hopefully they will reply to u soon...

Thanks!!!

I mean , how can they help me ,i mean : u do not know the answer .
Mean how  shud i contact then

i need to chat with some one to clear my doubts

Here in office gmail chatting disabled ... when can u be online next .. means today around 9-10 
or may tommmorrow


pls let me know
need to chat .. have some doubt which are still not clear and on monday is my presenation on the same topic 

And replying and waiting for response on this site , i cnt clear my doubts

pls help me 

Message Detail
============================================================
My gmail ID - aru


ur email id is [email protected]  ??




can u pls add me mine is [email protected]

are u online , can i chat with.. if u wont mind ..
if u r online then pls send me ur gmail id 

Nidhi when u use a Web Storage mechanism, the information is basically stored at the Client's end... (On the Client's machine.) You have to explicitly write code, may be a web service or use Hidden Fields to get the data and store it inside the Hidden field...

(Copied from the Link given ablove)

Passing data from Web Storage to server

Unlike Cookies, Web Storage data is not passed between the client and server with each and every request. If you wish to send the Web Storage data to the server you must device a programmatic way to do so such as a hidden field or an AJAX call. As far as ASP.NET web forms are concerned one neat way is to call a Web Service or a WCF Service from the client script and pass the data to the server. The server can then examine and process the data and may store it into a database.

In the example discussed in the next section, you will use jQuery to call Web Methods. The Web Methods perform two functions - they fetch data from the server so that client can render it as required and they persist the Web Storage data in SQL Server database. While dissecting the example, our focus will be on Web Storage related functionality and we won't go into the details of making AJAX calls using jQuery. (Check the example)

One question which i did'nt get from the link..

communication with server , when application is developed using web storage , state maintainence at server how is done 




pls answer this 

pls :)

Hey Nidhi, Check out this link.. It will help u understand the concept of web storage and Cookies..

http://dotnetslackers.com/articles/aspnet/Using-HTML5-Web-Storage-in-ASP-NET.aspx

Sorry if I confused you!!!

 Hi Shivanand Arur,

sorry  but i am not yet clear.

Web Storage has come as a replacement to cookies , and session cookies are sent with every http request to server for state maintainence.

If web storage is replacement to cookies then , when i m using web storage , then in replacement to cookie what i need to send to server for state maintainence .

As u say for that i need state management traditional approach .
cookie is a part of state management , so what does this mean here ?

Does web storage only has a role to save maximum data on local , in order to reduce hits on server , for the transactions where we can manage with the data on local system ?

and finally when we want the changes to reflect on server then we use same old approach.

pls reply .. i need to clear this doubt.

Thank u  :)

Hello Nidhi, if you want that the information to be consistent till the Session is alive then you have to use the State Management techniques.... As you said HTTP is a stateless protocol, the information passed to the Server is destroyed when the request is processed and a response is sent back to the Server. So to restore or retain the information, you have to use the State management technique

You can learn more about the State Management here...
http://www.c-sharpcorner.com/UploadFile/78d182/Asp-Net-state-management-techniques/

Please mark the answer as accepted, if it helped!!!
Thank you.