Looks like you need some throttling capabilities. This is not inherently supported in Axis2 but WSO2 Web Services Application Server<http://wso2.org/projects/wsas>(A.K.A. WSO2 WSAS) has support for throttling and you should be able to configure it to do just this. WSAS is made available under the same Apache License that Axis2 is available under (Actually WSAS is a complete web services runtime with enterprise capabilities built on top of Axis2).
Please do let me know if you need further details. You could find the project details here. <http://wso2.org/projects/wsas> [1] Thanks, Keith. [1] http://wso2.org/projects/wsas On Tue, Sep 30, 2008 at 2:38 AM, Richard <[EMAIL PROTECTED]> wrote: > Keith, > > > What do u mean by external and internal WS-Clients? > > External web service clients would be our customers which we give a WSDL > so they can call our web service. Ideally, we could indicate which > operations they are allowed to call but they are limited to the operations > which are for external use. > > Internal web service clients would be our web application which calls > operations which are intended for internal use. The web application might > also call operations which are intended for external use as well. > > > Well, If you use something like username token authentication on your > > service, you could access the username of the caller from within your web > > service and thus vary the action you need to perform. This is just > > one way of doing it though. > > Customers can use the same username to access the web service either via a > web services client outside of the firewall or by using the web > application which calls the web service from inside the firewall. > > Thanks, > Richard > > > Hi Richard, > > > > See comments inline. > > > > On Mon, Sep 29, 2008 at 11:09 PM, Richard <[EMAIL PROTECTED]> wrote: > > > >> Perhaps someone can help me with two questions: > >> > >> 1. Is it possible to create a web service where most operations can be > >> called by external ws clients but some operations can be called only by > >> internal ws clients. > > > > > > What do u mean by external and internal WS-Clients? > > > >> > >> > >> 2. The behavior of an operation needs to differ slightly depending on > >> whether an operation is called internally or externally--this can be > >> done > >> by checking the value an attribute or an element. Is there a more > >> transparent way to determine the ws caller so that behavior such as how > >> to > >> connect to the database can differ slightly. > > > > > > Well, If you use something like username token authentication on your > > service, you could access the username of the caller from within your web > > service and thus vary the action you need to perform. This is just one > way > > of doing it though. > > > > Thanks, > > Keith. > > > >> > >> > >> Thanks, > >> Richard > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > > -- > > Keith Chapman > > Senior Software Engineer > > WSO2 Inc. > > Oxygenating the Web Service Platform. > > http://wso2.org/ > > > > blog: http://www.keith-chapman.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
