|
From: Larry Bolhuis <lbolhuis@arbsol.com> > If the per session price were reasonable then I believe you are > correct. It can be fairly argued that each additional session is of some > value to the user and therefore should be payed for. However at the > price many packages extort for a 'session' it is not an option. It also > could be argued that it's unlikely the user is actively utilzing more > than one session at any given moment. Depends on the definition of > 'utilizing'. ===> I'll adopt a simple operational definition: If any of my application's programs are on your invocation stack, you are using my application. what can be simpler? > > Leif Svalgaard wrote: > > > > I don't get it. > > It would seem to me that a reasonable (and correct?) and > > fair way of doing this is to count the number of simultaneous > > sessions (no matter who the users are and how they are signed > > on and to what) that are USING MY APPLICATION at any time. > > This is very easy to do. +--- | 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 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.