What does DNT in the metadata mean?

109 views
Skip to first unread message

Mircea Chirea

unread,
Aug 19, 2014, 8:21:53 AM8/19/14
to rav...@googlegroups.com
{
 
"Raven-Entity-Name": "Orders",
 
"Raven-Clr-Type": "WebApplication1.Data.OrderDocument, WebApplication1",
 
"DNT": "1"
}

What does DNT mean here? Why do some documents have it and others don't?

Oren Eini (Ayende Rahien)

unread,
Aug 19, 2014, 8:24:16 AM8/19/14
to ravendb
Looks like it was added to your metadata via the http headers, maybe if you saved them on the browser?

It has no RavenDB meaning.




Oren Eini

CEO


Mobile: + 972-52-548-6969

Office:  + 972-4-622-7811

Fax:      + 972-153-4622-7811





--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Mircea Chirea

unread,
Aug 20, 2014, 3:59:13 AM8/20/14
to rav...@googlegroups.com
Oh... well that makes sense, IE sends that header. I suppose sending document metadata as HTTP headers is probably not the best idea given tha myriad of standard and non-standard HTTP headers.

Chris Marisic

unread,
Aug 20, 2014, 8:57:28 AM8/20/14
to rav...@googlegroups.com
HTTP headers seems like a perfect place for metadata for a HTTP Server.

Pretty much every single raven metadata is a nonstandard header, the metadata doesn't mean anything unless you make it mean something like through a bundle or query.

Mircea Chirea

unread,
Aug 21, 2014, 5:25:43 AM8/21/14
to rav...@googlegroups.com
Well except when you need to return multiple pieces of data, each with its own metadata (multi load, query results). Really the HTTP headers are meant for the request/response as a whole, not an individual document (as that breaks when you need to return more than one). Still, it's not as if it can be changed now without breaking every single app that uses RavenDB.

Chris Marisic

unread,
Aug 21, 2014, 10:54:33 AM8/21/14
to rav...@googlegroups.com
I don't accept this argument. When you issue a query or multi-get you are not asking for the same resource. So it is entirely reasonable (and nearly expected) that the headers returned would be different than an individual document. Since this is an aggregation of resources it makes perfect sense that the metadata to a single document would be included as part of the response, because the HTTP headers are metadata to the query.
Reply all
Reply to author
Forward
0 new messages