indeed there are many ways to skin a cat!
On Wed, Jan 19, 2011 at 1:34 PM, Gareth McCumskey wrote:
> ..
>
> Which is essentially what I suggested without the use of node.js
>
> On Wed, Jan 19, 2011 at 3:12 PM, Justen Doherty wrote:
>
>> ah yes, it helps when you read the full thread!
>>
>> i
..
Which is essentially what I suggested without the use of node.js
On Wed, Jan 19, 2011 at 3:12 PM, Justen Doherty wrote:
> ah yes, it helps when you read the full thread!
>
> in that case i would code it using node.js as a streaming socket server and
> get clients to login/update their he
ah yes, it helps when you read the full thread!
in that case i would code it using node.js as a streaming socket server and
get clients to login/update their heartbeat status using the client side!
On Wed, Jan 19, 2011 at 12:56 PM, strycore wrote:
> Hi,
>
> I have implemented such a thing in a
Hi,
I have implemented such a thing in a symfony project using APE Project
( http://www.ape-project.org/ ).
I tink APE has all the features you require, and it can show an up to
date user list (the default timeout
for a user leaving the website is something like 30 seconds, and
that's the worse ca
The requirement was to show a person as online for an IM chat client type
scenario so that as soon as possible after he leaves the page or closes
browser or logs out other people "People Online List" will be updated
correctly
On Wed, Jan 19, 2011 at 1:14 PM, Justen Doherty wrote:
> true - but th
true - but the requirement is for logged in users only, if you had a reason
for a user to stay on the same page for more than say, five minutes, then
you would need an ajax heartbeat to update the timestamp
we would have to understand the application a bit more rather than providing
technical solu
But you would need to update them not being logged in at some point. And
what if they just closed their browser window without logging out? Or what
if they log in and they have been surfing the site for the last two hours
... that logged in time would still stay the same
On Tue, Jan 18, 2011 a
i would have a 'last_logged_in' date against a user and every time a user
logs in, this timestamp is updated - once you have this time in the
database, then define an offset (say 2 mins or 180 seconds) and query
against the database for a count/users that are logged in..
On Tue, Jan 18, 2011 at 1
Or if the Presence information doesn't matter...
make a shoutbox...
On Jan 18, 9:24 am, Gabriel Petchesi wrote:
> You should look into server push technologies to get updated information
> from the
> clients.http://en.wikipedia.org/wiki/Push_technologyhttp://en.wikipedia.org/wiki/Comet_(program
