RFE: Include elapsed-time in results

[hunterhacker]

Seems like it may help people to have an elapsed time in the responses. For example: It lets you compare different queries reliably without concern for network latency overhead. It lets you record historic performance to a log.

At minimum this would be good on search results, but anything where there's a structured response it seems useful. And cheap on the MarkLogic side.

[eedeebee]

I like. Wonder if this is something modal/orthogonal you could turn on/off globally.

[hunterhacker]

Why would someone turn it off?

[eedeebee]

Maybe it's always on. All I could come up with for turning it off is

• leaky details I don't want my users to know
• every bit counts in bwidth especially if response bodies are small.

On Sep 27, 2011, at 3:00 PM, Jason Hunter wrote:

Why would someone turn it off?

Reply to this email directly or view it on GitHub: https://github.com/marklogic/Corona/issues/10#issuecomment-2217083

[hunterhacker]

I wonder how often will people send the raw response to their users?

Every bit counts, but only if it puts you over the next 1500 byte MTU limit. :)

[eedeebee]

I suspect some folks will write direct browser<->Corona apps on occasion. It's not good if the bulk of the response is eaten by data I don't care about:

E

On Sep 27, 2011, at 3:36 PM, Jason Hunter wrote:

I wonder how often will people send the raw response to their users?

Every bit counts, but only if it puts you over the next 1500 byte MTU limit. :)

Reply to this email directly or view it on GitHub: https://github.com/marklogic/Corona/issues/10#issuecomment-2217444

[hunterhacker]

If they do that, they have bigger issues than the browser seeing the elapsed time. A malicious browser could delete all their data.

We may want to think about how best to enable safe browser<->Corona communication.

[ryangrimm]

Included as an executionTime key or element, depending on the response type.