[Greasemonkey] API brainstorming: GM services?

[Andrew Hayward]

> What's wrong with uneval'ing into GM_setValue and evaling back out
> later? You can store values per-whatever (page, domain, *, etc).

If there's enough demand for storing objects persistently, could that 
not be written "natively" into GM_(set|get)Value? The author passes in 
an object, and gets an object back - s/he doesn't need to know if it's 
been (un-)eval'd on the way.

Just a thought.

- A.