Set the page content type so that nothing else is added by Domino to the output. For JSON, setting it to "text/javascript" would be appropriate. Then, add computed text to the page to generate the JSON--can't add fields since this is a page, but computed text works just fine in this situation. The computed text could be an @DbLookup, and could even make use of parameters passed in the URL (use @UrlQueryString inside the computed text to get the params from the URL).
Although it wasn't JSON, I've used this technique before, and it worked well. Seems to me it would just be a matter of getting the formula to pump out the right syntax for JSON. The other caveat is a familiar one: the computed text can't return more than 15K.
Question remains, would this be any better than an agent...
How about using a page instead of an agent...
Set the page content type so that nothing else is added by Domino to the output. For JSON, setting it to "text/javascript" would be appropriate. Then, add computed text to the page to generate the JSON--can't add fields since this is a page, but computed text works just fine in this situation. The computed text could be an @DbLookup, and could even make use of parameters passed in the URL (use @UrlQueryString inside the computed text to get the params from the URL).
Although it wasn't JSON, I've used this technique before, and it worked well. Seems to me it would just be a matter of getting the formula to pump out the right syntax for JSON. The other caveat is a familiar one: the computed text can't return more than 15K.
Question remains, would this be any better than an agent...