On 27 Feb 2012, at 22:26, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hernán,
>
> On 2/27/12 3:04 PM, hernan wrote:
>> I've a web service. In order to do a request, a user specifies a
>> username and password via web service parameters along with web
>> servic
On 27 Feb 2012, at 22:18, Hassan Schroeder wrote:
> On Mon, Feb 27, 2012 at 12:04 PM, hernan wrote:
>
>> - how to or where to place and access an object shared by all tomcat threads
>>
>> And I'd like to have a solution that can be extended to many tomcat
>> instances (in different servers).
>
>
2012/2/27 hernan
>
>
> The process may take some seconds or a few minutes to be completed. I'd
> like to limit the number of client requests per user.
>
Why not do you use Tomcat's valves mechanism ?
You can implement a request filter on a Context scope
Where store the counter of requests ?
Mem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hernán,
On 2/27/12 3:04 PM, hernan wrote:
> I've a web service. In order to do a request, a user specifies a
> username and password via web service parameters along with web
> service parameters. The web service server, checks user and
> password and
On Mon, Feb 27, 2012 at 12:04 PM, hernan wrote:
> - how to or where to place and access an object shared by all tomcat threads
>
> And I'd like to have a solution that can be extended to many tomcat
> instances (in different servers).
Why not just keep counters in an in-memory store like e.g. Re
Hi,
I'm looking for ideas/suggestions/patterns about limiting concurrent
requests by user. May be you have tackled this kind of problem
previously and I'd like to heard your opinions.
I've a web service. In order to do a request, a user specifies a username
and password
