CODEWITHSUNDEEP
javascriptangularjshtmlasp.net-web-api
micronyks
micronyks

Reputation: 55443

Asp.net web api Session

I'm not getting the concept web api and session.

I've created asp.net web api project and integrated angularjs in it.Every time I'm gonna call web api.

I have read the articles which state its not good to use session in Web api. I do understand that web api is stateless approach. I do agree. stil there is a way to use session.

First question: If, after login, i want to show user name on every page what should i do with web api approach????

second question: they say don't use session in webapi. then what is the other way/approach to store client information safely.

If I use HTML5 local storage, it can be editable. If cookie is used, it can be deleted.

What and how should I do it for user till application is in running mode?

Upvotes: 4

Views: 1492

Answers (3)

Gerben Rampaart
Gerben Rampaart

Reputation: 9945

This is where semantics often clouds the discussion. People confuse the Session object with statelessness. And often say: 'don't use session because it isn't stateless!'.

However they really mean that you should strive to have your the restful calls to be idempotent, meaning they don't change their behavior depending on whatever it is you do in the background.

Session, or the runtime-cache, or whatever it is you use to cache data, has no effect on your stateless design, because really, what's next? Your database is statefull too? And you shouldn't read data from that? Nonsense obviously; your underlying storage, if it's in-memory or on disk has no reflection on your state to the client.

Although I feel @MajoB makes other valid points about not using the session object, there is really no harm using some kind of cache in the web api, session or something else. But never let the fact if something is IN session return a different result then when something is OUT of session.

Upvotes: 2

Mikalai
Mikalai

Reputation: 1525

I would recommend you use asp.net identity and render user information on server.

Upvotes: 0

Marian Ban
Marian Ban

Reputation: 8188

I would recommend you to avoid asp.session because it may cause performance issues and can expire anytime regardless of your application state, does not scale on cloud, it will block concurrent ajax requests). Better approach would be to use HTML 5 storage mechanism especially in conjunction with AngularJs (you can use ng-storage https://github.com/gsklee/ngStorage).

Upvotes: 1

Related Questions