>>Yes, I wasn't implying that only WinDev handles the server/client stateless issue. I was just pointing out to Victor that choosing WebDev to evaluate WinDev requires not only evaluating the language/IDE differences but also thinking about stateless application development (assuming he had not already done such apps).
>
>I agree - jumping from stateful to stateless requires not just a different mindset, but a different head :). To anyone who didn't grow that other head yet, finding that he needs it while just evaluating a new platform would be extremely confusing.
WebDev can store state of controls for you, amongst other things. iow, it is built with this problem of stateless-ness in mind and provides a "dual" programming paradigm/IDE, if I can phrase it like that, which helps you think about what must happen at the client and what must happen at the server.
In the End, we will remember not the words of our enemies, but the silence of our friends - Martin Luther King, Jr.