Title: RE: Witango-Talk: Server Provided Info: who is loged on? (probably not entirely OT)

I was inclined to use a DB because of all helping functions in the DBMS.
An array to do what I need will have at least 2 cols: userReference & time-of-request.
For each request, I will have to search the array to find the row and update the time or create a new row.
When I need the number of users and the time left for each until timeout, I need to sort by time and keep the rows within the TIMEOUT minutes.

Not difficult, but time consuming non the less.
It is justified if it serve a purpose (collecting data for statistics and marketing, as it seems to be your case) but mind boggling otherwise because the server already has all this info and could provide it through a metatag with almost no overhead.

Thank you again for your reply.
- Mike
[EMAIL PROTECTED]
 

-----Original Message-----
From: Roland Dumas [HYPERLINK mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]]
Sent: Monday, June 12, 2006 15:18
To: [email protected]
Subject: Re: Witango-Talk: Server Provided Info: who is loged on? (probably not entirely OT)


On Jun 12, 2006, at 3:11 PM, <[EMAIL PROTECTED]> wrote:



        Thank you for your reply.

        Yes, it is not complicated to do the monitoring myself...BUT:
        I have to keep track of every user and update the date+time when they make a request; and to get the current status, I have to do another search in the DB.


No you don't have to hit up a database. Just create a domain scope array. A tiny little include you can toss into all your tafs or .tml pages.

I whipped up one so I could tell how many people were on the site, what they had in their shopping carts and a couple of other things. When their session expired, the array lost that row.  So an admin could tell who is there, what they were looking at and what was in the carts. (when the session expired, it wrote some of the info to a table for analysis, but that's one db hit per session.


        It is not difficult, but this is overhead (eats CPU resources and accesses the DB) which is not necessary because it is duplicating something the server is doing anyway.

        I was just wondering if the info is available and I missed it; if not, why Witango does not provide it.

        Thank you,
        Mike
        [EMAIL PROTECTED]

        -----Original Message-----
        From: Roland Dumas [HYPERLINK HYPERLINK mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] HYPERLINK mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]]

        Sent: Monday, June 12, 2006 12:58
        To: [email protected]
        Subject: Re: Witango-Talk: Server Provided Info: who is loged on? (probably not entirely OT)


        On Jun 12, 2006, at 12:35 PM, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> wrote:



                Hello all,

                1-
                I know this issue has been discussed long ago and I apologize for reopening the subject.
                One useful piece of information (for administration purposes) that the Witango server could offer, is how many users are logged in and how much time is left before the timeout (or equivalent).

                I could not find this capability described anywhere, but it might be mentioned somewhere and I just missed it.

                Does anybody know if this is possible and/or provide a hint to the appropriate documentation?
                (I am not interested in a custom solution; I know I can keep track of users but this means constant overhead while collecting this info from the server implies almost no overhead)

        don't think it's possible without creating your own function. Having said that, it's not so hard to create a domain scope array that is tracking who is there, time since last hit (and therefore time to expiration)

        ________________________________________________________________________
        TO UNSUBSCRIBE: Go to HYPERLINK HYPERLINK http://www.witango.com/developer/maillist.taf http://www.witangocom/developer/maillist.taf HYPERLINK http://www.witangocom/developer/maillist.taf http://www.witangocom/developer/maillist.taf <HYPERLINK "http://www.witango.com/developer/maillist.taf"http://www.witangocom/developer/maillist.taf>


        --
        No virus found in this incoming message.
        Checked by AVG Free Edition.
        Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006



        --
        No virus found in this outgoing message.
        Checked by AVG Free Edition.
        Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006
         

        ________________________________________________________________________
        TO UNSUBSCRIBE: Go to HYPERLINK http://www.witango.com/developer/maillist.taf http://www.witangocom/developer/maillist.taf



________________________________________________________________________
TO UNSUBSCRIBE: Go to HYPERLINK http://www.witango.com/developer/maillist.taf http://www.witangocom/developer/maillist.taf


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006



--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.8.3/361 - Release Date: 6/11/2006
 

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to