BorlandTalk.com

Glenn Thimmes · Guest

As each user logs into my web broker application, I am needing to find out
how many users are already logged in and if the limit is reached log the
event and send them to a 'max concurrency reached' page. This is difficult
since I do not have separate application and sessions levels.

I see I might be able legitimately reference the TWebApplication as
(self.Owner as TWebApplication), but it looks like the active module list is
private anyway. Alternatively, if I could create an object in the
initialization of the ISAPI dll that would be visible to all instantiated
DataModules, they could each use that object to check, set the refcount of
current connections.

Any suggestions on how I might accomplish this type of functionality in a
Web Broker application? I see that this would be simple with WebSnap,
though WebSnap itself is NOT simple.

Thanks.

Glenn Thimmes · Guest

So should I assume that it is not possible to find out how many web modules
are currently in the active module list?

"Glenn Thimmes" <glennthi (AT) NoSpam_msn (DOT) com> wrote

Dave Hackett · Guest

Application.ActiveCount = # Active WebModules modules processing requests
Application.InactiveCount = #WebModules in memory - not current processing a
web request

DaveH

"Glenn Thimmes" <glennthi (AT) NoSpam_msn (DOT) com> wrote

Glenn Thimmes · Guest

Thanks for your help, Dave. I've added a response.Content :=
Application.ActiveCountin my web app so that I could confirm that this is
behaving the way I would like. When my first browser is opened, it comes up
as 1, then any following browsers that hit my page still get an ActiveCount
of 1. Right now I should be seeing an active count of about 10, but it
still gives me 1 as the count.

What am I missing?

"Dave Hackett" <dave.hackett (AT) ns (DOT) sympatico.com> wrote

DaveH · Guest

You would need to have more then 1 browser hit the server at the exact same
time in order to see a larger number.

Think of this way...

1) A web request comes in
2) WebBroker looks at the InActiveList. If there is a Web Module available,
it gives the request to it and moves the Module into the Active list. If
there isn't, it creates a new WebModule, puts it into the active list and
gives it the request.
3) The Web Module handles the request and sends back the response.
4) WebBroker moves the Web Module back into the InActive List

So, since your Web Module is so fast (it just returns the count, right?), it
is probably finished the first request before the next one comes in - hence
Active Count = 1.

As a test, put a delay in the Action Handler - like a for loop. Don't
forget to actually use the stuff in the for loop or the compiler will strip
out the "unused" code.

DaveH

"Glenn Thimmes" <glennthi (AT) NoSpam_msn (DOT) com> wrote

Glenn Thimmes · Guest

Thanks for the explanation. That makes perfect sense to me now, and I
really should have seen that already. Shifting to this type of sessionless
paradigm is difficult when I am use to having a session level object around
during multiple requests.

Thanks again.

"DaveH" <daveh (AT) sympatico (DOT) com> wrote