[wp-trac] Re: [WordPress Trac] #1476: WordPress Update Notification

[WordPress Trac]

#1476: WordPress Update Notification
----------------------------+-----------------------------------------------
 Reporter:  mdawaffe        |        Owner:  pishmishy  
     Type:  enhancement     |       Status:  assigned   
 Priority:  normal          |    Milestone:  2.3 (trunk)
Component:  Administration  |      Version:  2.1        
 Severity:  normal          |   Resolution:             
 Keywords:  update upgrade  |  
----------------------------+-----------------------------------------------
Comment (by santosj):

 What about mirrors? You can hit the original server once a day or every 5
 hours to get the trusted mirrors (that are up and responding). Then
 randomily hit one of them.

 You will most likely find that trying to get from another server is going
 to take a while. Something like this would probably need a real cron job,
 because the function might slow down the site terribly.

 Replying to [comment:27 pishmishy]:
 > Replying to [comment:26 westi]:
 > >
 > >  1. Only one request should be made each time to the update
 notification server.
 >
 > Agreed.
 >
 > >  1. Downtime on the update server must not slow the load time of the
 blog - i.e. at least use ajax like the dashboard does and probably run the
 check calls using the builting cron functionality.
 >
 > The dashboard feeds don't work if Javascript is disabled. I don't think
 this is acceptable for something more critical which is why I've avoided
 javascript and ajax.
 >
 > I don't know much about the cron functionality - I'll look into that -
 will have to be careful to make sure that WordPress installs don't all hit
 the server at the same time.
 >
 > >  1. XML-RPC is a bit heavy for this as it requires processing on the
 serverside at the update beacon - a REST based service would be much
 better - e.g. http://update-service.org/wordpress/<version>/ would return
 the update info for <version> of WordPress.
 >
 > Agreed - far less complicated. I'll work on (at least ;-)) the two
 points we've agreed on this evening.
 >
 > James

-- 
Ticket URL: <http://trac.wordpress.org/ticket/1476#comment:28>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software