WAP and Session ID's (Score 1)

WAP doesn't create it's own session ID's. Session ID's are set by the Servlet engine. How those ID's are passed around between GET/POST's is different. If you are depending on Cookies for session management, then you are going to run into problems with WAP phones, Palm devices and people who disable Cookies. Stay away from using Cookies for session management, use URL rewriting instead. Posted by Cliff on Sunday May 21, @12:17PM from the getting-it-working dept. Yousef asks: "We're trying to develop a WAP enabled Webserver, that can work with Java (Servlets). Currently the only working option is M$ IIS running the New Atlanta plugin. Now I'd rather NOT run IIS, so if anyone else has a solution to this, it would be much appreciated. We've tried Inprise IAS and Apache JServ (We're deploying to a Sun Solaris box). Any help would be nice. Getting the servlets to run is quite easy -- The problem is getting them to work with WAP!" "WAP creates its own session ids, and that stops other serverside objects from sharing the same objects. In short, we have an existing Servlet based system. Now we are trying to incorporate WAP into it (WML). It seems to us as though WML passes cookies around differently to HTML: HTML stores them with the browser, and WML stores them on the server. We've tried just about every server under the sun, and they all behave in the same way."