Additional key documentation?

[Texas]

So, that means it does actually retrive the newest data? Or is the POST call used to just remove the item? Sorry if the answer seems obvious, I haven't really dealt with POST calls much so I don't know much about them.

[Wormopolis]

It updates the value stored on the server, but I believe it also updates the array in memory. I never setup an experiment to test the on page value after a push because I usually save key changes until last - and then follow with a page change anyways to make sure everything gets updated.

[Chris]

From my own observations almost all AJAX calls (not just key related calls) to the Proboards server carries with it a payload that updates the locally saved key data for all plugins (if there was a change) among other things such as a flag that basically says whether the search server is still functional or not. There were however some observed inconsistencies which I attributed to originator sometimes (?) not getting notified of actions they had originated (i.e. an [IP/session cookie/unknown common denominator?] that initiated an action that resulted in a change might not get a notification update of the change they caused to occur). There's also a possibility that the feature is scaled back during heavy network traffic.

The editable plugin in this post explores this undocumented feature and might help you get a handle on the situation. However keep in mind that the plugin might violate parts of the coding guidelines since it may have morphed and took on the role of exploration rather than concentrating on some tangible end goal. Ultimately it would be great if Proboards documented this behavior with emphasis on explaining the discrepancies to take any of the guess work out of the equation.