Jump to content

Scheduled down-time on all sites Monday, 2nd December 2013


Dark0ne

Recommended Posts

  • Replies 119
  • Created
  • Last Reply

Top Posters In This Topic

Updated the OP.

 

16:00 GMT

Skyrim has successfully been converted and the maintenance work is now done for that site. We are now proceeding with the other sites (that should take a lot less time due to their reduced size). As we're now in a status of limbo between the two different site types (centralised and uncentralised) things will probably look a bit odd. Best to wait until we're fully done before exploring too much. We are busy converting all the other sites and as such you should expect the service to be intermittent at best due to the heavy load this will place on the servers.

Link to comment
Share on other sites

You could save a significant amount of server hits and improve responsiveness by properly implementing the tabs on the mods pages.

 

So many unnecessary server requests simply when the user switches back and forth between discussion, description, files... all you have to do in Javascript when it does the AJAX request is to store the content in a unique DIV for each TAB.

 

It doesn't matter if someone made a new posts in the last minute does it? You can always reload the page to see the most up to date comments or changes if you're living on the edge...

 

Then when the user switches back and forth it will also be instantaneous and thus far more responsive.

 

It would make more sense that you don't do this on the client side if one tab contained the edit mod options, because then it would invalidate the contents of another tab after you clicked "save" or "update".

 

Complex tab based web apps would have a flag on each tab that indicates whether the tab contents is still valid. Clicking "update" on one tab would flag another tab contents as "outdated" so when the user clicks the other tab, the AJAX request is pulling newer/fresher content. It's really a very simple logic based on principle that 90% of the requests are going to be not the initial page load, but people just going back and forth between tabs on the same mod. All completely unnecessary server hits.

 

Here on the Nexus the edit features are in a different page altogether so there is not even any need for the "tab invalidation" logic, all you have to do is pull the contents in a div that is originally empty, and then when the user clicks a tab, checked whether it was loaded already or not. If it was loaded, simply switch the div visibility and no need to do another ajax request.

 

Edited by ecirbaf
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...