Hello Everyone,
Thanks to all who responded with great ideas and interesting suggestions
(especially Raaj for the numerous replies and excellent feedback). This
thread has taken many different twists and many ideas have been exchanged.
Great.
However, in order to proceed I think I'll reverse my approach and instead
of asking a question (as I set out at the start of this thread) I will
explain the problem we would like to solve.
We have developed a Server-Side Java / Client-Side JavaScript video
application for a government client who for many reasons does not want the
public to inundate his/her web services with multiple requests from the
same surfer. i.e. There are currently 20 feeds and the client would like
it such that no person from the public can access more than one feed at a
time. (Internally, on the intranet side the story is very different and
the client doesn't care how many feeds are opened by an employee).
Since we are using Servlets anyways, I thought it natural to try to come up
with a mechanism to limit access to one active session per user that
translates to only one active browser page. IN the grand scheme of things
if the limit can only be imposed browser wide then I'm not sure that there
would be a real major problem since most people would at most probably have
IE and NN (if they even have both installed at all) which would result in
two active feeds (quasi-worst case) per surfer.
If the "remote host address" is unique for any given surfer at any one time
then bingo we should be able to solve our problem - if not then we have to
look for other solutions.... All along, what I was looking for was this
unique identifier (for a given dialup session say) that I could use to
limit multiple video feed requests from the same surfer.
Any comments....
--Nikolaos
On Friday, January 14, 2000 2:28 AM, Rajendra Mishra
[SMTP:[EMAIL PROTECTED]] wrote:
> I would suggest that you write a dummy servlt and check it out. Of
> course it all depends upon whether the ip-addres can be used as the
unique
> identifying attribute of the user across multiple sessions in idfferent
> browsers...
On Friday, January 14, 2000 5:39 AM, Thor HW [SMTP:[EMAIL PROTECTED]] wrote:
> Why are you trying to solve this? What sort of application flow are you
> trying to accomplish?
On Friday, January 14, 2000 10:33 AM, Kevin Jones [SMTP:[EMAIL PROTECTED]]
wrote:
> Another question, what happens if the user moves from machine to machine?
or
> has different logon credentials, does this matter?
On Friday, January 14, 2000 6:36 PM, Mikhail A.Golovanov
[SMTP:[EMAIL PROTECTED]] wrote:
> The server (Apache JServ in this case) has two sessions from one user.
The
> session IDs (and the HTTPServletSession objects are different, the remote
> address is the same.
>
> Isn't this a solution? I use it considering a bundle of "agent" sessions
in
> the servlet context with the same remote address as a single "user"
> session, particularly to serialize user data update requests.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
