Alternative to HTTP Cookies? -

They say that I personally believe that on a web app, "Cunning" should be the way.

Say, currently it works in a distributed environment where xyz.com has many pools and the server (which I know):

1. User log xyz. Com
2. The login module of xyz.com drops a cookie on the client's local machine.
3. Now, when the client goes to feature 1 of xyz.com, feature 1 checks a pool for local cookies, if it finds it and if its expired, then the feature 1 assumes that the customer is good and carries him in.

So, the feature1 relies on the customer due to the cookie dropped by the logged module on the eyes.

But I feel a basic fault here on stage 3. What if a hacker clones a cookie and tries to do something? (Which is the first obvious thing that a hacker will try, sniffing cookies)

So, is there any alternative? - How will web storage be stored, store stored items in the future? Or will the cookies rule?

There is no search for a clear answer, because nobody is interested in different approaches to this inquiry.

Thanks

One of these basic principal, and I mean that on the server The state is not to be stored, if there is no state on the server, there is no need for a cookie to see that situation.