Consider changing the header value to a value type that is either a single string or a string array #240

davidfowl · 2015-03-30T00:37:55Z

Many of the headers are a single string value but we pay the cost of allocating an array in all of our APIs when setting a headers. We can avoid this by making the feature interface a value type what represents either a string or string[].

/cc @lodejard

davidfowl · 2015-06-13T19:26:34Z

On top of this, we should enumerate the set of known headers and optimize the setting/getting of them.

davidfowl · 2015-08-17T09:27:38Z

Closing this as dupe of #361

Tratcher mentioned this issue May 28, 2015

ApiReview: How can we efficiently represent items that may be either singular or plural #268

Closed

Tratcher added the needs design label Jun 12, 2015

Tratcher assigned davidfowl Jun 29, 2015

Tratcher added this to the 1.0.0-beta7 milestone Jun 29, 2015

muratg removed the needs design label Jul 13, 2015

davidfowl removed their assignment Aug 17, 2015

davidfowl removed this from the 1.0.0-beta7 milestone Aug 17, 2015

davidfowl closed this as completed Aug 17, 2015

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Consider changing the header value to a value type that is either a single string or a string array #240

Consider changing the header value to a value type that is either a single string or a string array #240

davidfowl commented Mar 30, 2015

davidfowl commented Jun 13, 2015

davidfowl commented Aug 17, 2015

Consider changing the header value to a value type that is either a single string or a string array #240

Consider changing the header value to a value type that is either a single string or a string array #240

Comments

davidfowl commented Mar 30, 2015

davidfowl commented Jun 13, 2015

davidfowl commented Aug 17, 2015