Add a block that can be displayed on the website that shows the status of the guilds realm.

US: http://www.worldofwarcraft.com/realmstatus/status.xml for the US servers.
EU: http://www.wow-europe.com/realmstatus/status.xml (I get a parse error when trying to access. Anyone??)

CommentFileSizeAuthor
#2 wowarmory-751236.patch4.28 KBbspellmeyer

Comments

trentoncolley’s picture

World of Warcraft (EU) doesn't have a status.xml file like the (US) version of the site. However you can use this RSS Feed possibly to parse the server status.

http://www.wow-europe.com/realmstatus/index.xml

:-)

bspellmeyer’s picture

Version: 6.x-1.x-dev » 7.x-2.x-dev
Status: Active » Needs review
StatusFileSize
new4.28 KB

The attached patch adds a basic realm status block for US and EU realms. As this patch is for the Drupal 7 version, I updated the version to Drupal 7.x-2.x.

trentoncolley’s picture

Ok thanks, There is one issue from what I see though. This is that it doesn't store the status in the database or as a variable. The reason we would want to do this is to stop a ban from worldofwarcraft.com or wowarmory.com for requests. If I stick a timestamp in the database that it checks against every time it pulls the information and if it's over for example 5mins it will refetch the realms status and update it in the database. The way it's written as well would mean that for every user that visits the site would send off a request. Not that it's likely a guild website would have exceptionally high traffic, but to avoid the ban which would likely stop both a roster update and the realm status from working I think it needs to be implemented.

As I am also working on linking the characters to user accounts I figure the best way to do this is by creating a custom node for each character. As for the realm status I don't think it's necessary to save the realm status to each individual character in the guild and it'd be sort of odd to create a row [0] for just that status. I think to some extent to implement a new database structure needs to be implemented.

I'm thinking that guild information such as realm status, an array of characters that links to a character table, etc. (keep the guild specific information seperate) would be the best approach. The characters would then hold their specific information in a seperate table or within the node.

Anyways it's a lot to take in but I think it's the best way to go forward while implementing the new features to keep it as clean as possible. Unfortunately I haven't really had anyone to bounce ideas off of, seems like you care about the project enough perhaps you got some ideas?

Thanks for the updates they help a lot.

trentoncolley’s picture

Status: Needs review » Needs work
bspellmeyer’s picture

I'll implement caching as soon as I get to it today and post a new patch. The realm status won't be saved per character but per realm into Drupals default cache table.

For the database tables / schema updates: I don't think this has anything to do with the realm status block and therefore should be moved into a separate issue.

trentoncolley’s picture

Sounds good.