Our application currently exposes web services built with WSDL 1.1 and SOAP 1.1 following the w3c standards below:

> 
> <http://schemas.xmlsoap.org/soap/http>
>  is the WSDL 1.1 binding for the SOAP
>  1.1 HTTP binding.
> 
> 
> 

We want to revamp our web services to be **Scallable, Secure and Easy to Use**

Easy to use refer to the fact that at this moment web services do not incorporate any of the business logic on that layer. Basically, our current web service could be seen as a import/export service for external/3rd party developers. 

This effort brings me to the question: 

> 
> What do I have to expect of a revamp
>  of our web services that are
>  scallable, secure and easy to use?
> 
> 
> 

---

Current issues with our Web Services

* You have to login (1st transaction) to receive a token (keeps session in memory) in order to use them.
* Is not scalable because any developer could open 20K sessions and crash the web service server.
* Is not secure because the same users from the admin of the site, could use the web services.
* It is not easy to use, because the web service do not incorporate any of the business logic.

The reasons our clients like our web service interface is because, any data element they add in the web application it will be exposed in the web service (wsdl) definition immediately. 

---

One more bit of information:

I was hoping to confirm my theory that all the points mentioned above as issues could be solved if we implemented our web services in a RESTful way. Since each transaction will not cause memory buildup and each transaction will incorporate a security settings with public key or similar. 

Either way, JRO, is right maybe if I slice the question in a series I will get better result. I will keep this question here until the end of day, if I get nothing better I will take JRO advice.