Talk:GridInfo

Revision as of 05:46, 3 May 2011

documentation viewer side

LL 1.x based viewers

Hippo viewer (and any viewer using its patches) get the grid info using HTTP GET, the only answer accepted is 200 OK, the uri is hardcoded to <loginuri>/get_grid_info

The xml tags that are parsed are (without quotes, 'or' means values of both tags are parsed to the same variable):

• "gridnick"
• "gridname"
• "platform"
• "login" or "loginuri"
• "welcome" or "loginpage"
• "economy" or "helperuri"
• "about" or "website"
• "help" or "support"
• "register" or "account"
• "password"

Imprudence parses additionally

• "search"

The result of that is stored in a llsd-xml array file which contains additional keys, though those are not parsed from the grid info.

LL 2.x based viewers

Kokua currently gets the grid info using HTTP GET If-Modified-Since and updates an existing entry accordingly, the only answer accepted is atm 200 OK (301 302 303 redirect are handled transparently), the uri is hardcoded to <loginuri>/get_grid_info

The xml tags that are parsed are (without quotes, 'or' means values of both tags are parsed to the same variable, wip state of 110429):

• "login"
• "gridnick"
• "gridname"
• "welcome"
• "register"
• "password"
• "help"
• "about"
• "helperuri" or "economy"

The result of that is stored in a llsd-xml map file which contains additional keys, one of which is the date of the last access; any other key is not related to the grid info.

Proposals for a future grid info version

• any http method in LL based viewers automatically parses from/to llsd, any other behavior needs manual intervention: override the raw data retrieval method for avoiding the xml erroneously being parsed as llsd, parse raw data to xml, parse the xml to llsd. If a future version of the grid info provided a llsd map it would solve a lot of headaches.
• one key per value (no "helperuri" or "economy", the future grid info will support only one of both)
• no keys for data that is retrieved better in a different way - like using the login message, or a capability ("search")
• if there is a convenient way to let the viewer know where the grid info is located the viewer has all it needs to know, if the grid info contains the loginuri. The current model is lookup the info at <loginuri>/get_grid_info -> override loginuri by the value from the grid info.
• a unique, stable identifier for the grid would be very handy. Hippo identifies grids by the gridnick, which will fail as soon as there are several grids using the same nick. Kokua identifies the grid by the loginuri, which is impractical if a grid changes it.

ArminWeatherwax 13:39, 29 April 2011 (UTC)