× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Counting users
  • From: "Hall, Philip" <phall@xxxxxxxx>
  • Date: Tue, 31 Jul 2001 11:49:54 -0500

> The issue you have (and you have already stated you know it) 
> is that for
> dumb terminals that have multi session support (those that 
> have the Atl+Jump
> support), these multi-sessions appear as separate devices - 
> those are going
> to be the difficult ones to count as 'one' user.

Thinking about it some more (and it's been a long time since I dealt with
controllers & devices, so my ports & sessions might be mixed up) for a
multi-session device (like a 3487 InfoWindow) don't they all have to be on
the same ws-controller, same port, but different session number ? Although
that doesn't cover the chance that the user is signed on to 2 single session
devices that are on the same controller port, but it does help...

Also if you're using the 6050, 2661, 9146 or 9148 ws-controllers, they can
be set to use the same session number for all of the session that the device
supports.

Using 'rules' like these, you might just be able to get a fairly close
handle on usage.

--phil
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.