- From: <Joachim.Peer@unisg.ch>
- Date: Tue, 26 Oct 2004 18:48:22 +0200
- To: Cristóvão Bento <cbento@criticalsoftware.com>
- Cc: www-ws@w3.org, www-ws-request@w3.org
hi Cristovao, > As far as i understood, web services are stateless by definition. i don't know which definition you are refering to, but i do not think that such a restriction would be useful. Sure, HTTP is a stateless protocol (maybe that's what you are referring to), but you can use things like session tokens to group multiple stateless calls into (stateful) sessions. e.g.: 1. login(username, pwd) => return sessoin token sid 2. listItems(sid) 3. addToCart(sid, someItem) 3. checkout(sid) > Although i would like to know what are the developments in stateful > Web Services. Is it possible already to have a full server running > and responding to requests like for example a Windows DCOM Service? > or a CORBA Server. yes, this is already possible > > When this will be possible with Web Services? to have mass > processing server running while some application server is running... check out Apache Axis (http://ws.apache.org/axis/index.html) and/or WS-enabled application servers like JBoss, etc. best, Joe
Received on Tuesday, 26 October 2004 16:48:34 UTC