|
|
|
||||
|
Welcome to the GoFuckYourself.com - Adult Webmaster Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact us. |
![]() |
|
|||||||
| Discuss what's fucking going on, and which programs are best and worst. One-time "program" announcements from "established" webmasters are allowed. |
|
|
Thread Tools |
|
|
#1 |
|
Confirmed User
Industry Role:
Join Date: Feb 2005
Location: Los Angeles
Posts: 1,531
|
Server contacting browser...technical thread...
Is there any way that the server is able to send an unsolicted message to a specific client?
For example, I am working on this dating site, and when I make changes in the admin panel, the test browser almost immediatly reboots and asks for my login again - this is normal action. There are only 2 ways I can think of that this can happen: 1) The browser is contacting the main website every second to know if anything has changed. 2) The server, is somehow able to send a message to the browser... I understand how to do method 1. The browser pings the website for some sort of session or update data or whatever. But! Is method 2 even possible? Is there any way that the server is able to send an unsolicted message to a specific client? I would never make a wesite "ping the server every second to find updates", since with 10,000 online visitors, that would be a huge load. So if there is some way to do method 2 that would be awesome. Does anyone know if this is possible? Ideas?
__________________
www.gimmiegirlproductions.com |
|
|
|
|
|
#2 |
|
Confirmed User
Industry Role:
Join Date: Sep 2003
Location: NZ
Posts: 673
|
If the browser that's updating the admin section opened the "test browser" window it could be instructing it to reload the updated site.
If the "test browser" is entirely separate then it must be periodically checking with the site for changes. There's really no way the site could be reaching out to the browser.
__________________
-- react |
|
|
|
|
|
#3 | |
|
Confirmed User
Industry Role:
Join Date: Feb 2005
Location: Los Angeles
Posts: 1,531
|
Quote:
I didn't think there was a way for the server to reach out to the browser...I just wanted to confirm that there wasn't any new trick I wasn't aware of.
__________________
www.gimmiegirlproductions.com |
|
|
|
|
|
|
#4 |
|
I help you SUCCEED
Industry Role:
Join Date: Nov 2003
Location: The Pearl of the Orient Seas
Posts: 32,195
|
Hmmm, wouldn't there be privacy issues involved?
|
|
|
|
|
|
#5 |
|
So Fucking Banned
Join Date: Aug 2008
Location: Just Blow Me
Posts: 10,551
|
bump bump
|
|
|
|
|
|
#6 |
|
Confirmed User
Join Date: Feb 2002
Location: ICQ: 251425 Fr/Au/Ca
Posts: 6,863
|
Sure, you check the Modified headers sent by the browser, or the Cache-Control headers..
|
|
|
|