# .NET Client and CoreFX Lab

**URL:** <https://discuss.elastic.co/t/net-client-and-corefx-lab/70761>\
**Category:** Elasticsearch\
**Created:** [January 6, 2017, 9:24am UTC](https://discuss.elastic.co/t/net-client-and-corefx-lab/70761 "2017-01-06T09:24:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![KodrAus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kodraus/32/22798_2.png) [@KodrAus](https://discuss.elastic.co/u/KodrAus)\
**Post date:** [January 6, 2017, 9:24am UTC](https://discuss.elastic.co/t/net-client-and-corefx-lab/70761/1 "2017-01-06T09:24:13Z")

</div>

@forloop have you got any opinions on the .NET [CoreFX Lab](https://github.com/dotnet/corefxlab) stuff? Particularly whether these APIs, if they're ever stabilised, could be put to good use by the .NET Elasticsearch client?

The abstraction over various sources of memory is really neat, and it's being used for UTF8 strings and more efficient JSON serialisation.

Pipelines also look like they'd be an effective way to build connection pools.

---

<div class="post-metadata">

**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\
**Post date:** [January 9, 2017, 9:59pm UTC](https://discuss.elastic.co/t/net-client-and-corefx-lab/70761/2 "2017-01-09T21:59:56Z")

</div>

Most definitely!

The key thing is stability; I'm keeping an eye on this so if/when they're at the point of RTM, we can use them as part of the client generator we're hacking on

---

<div class="post-metadata">

**Author:** ![KodrAus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kodraus/32/22798_2.png) [@KodrAus](https://discuss.elastic.co/u/KodrAus)\
**Post date:** [January 9, 2017, 10:46pm UTC](https://discuss.elastic.co/t/net-client-and-corefx-lab/70761/3 "2017-01-09T22:46:24Z")

</div>

Is that client generator work floating around in the open somewhere? I wouldn't mind watching that unfold.

---

<div class="post-metadata">

**Author:** ![forloop](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/forloop/32/9021_2.png) [@forloop](https://discuss.elastic.co/u/forloop)\
**Post date:** [January 9, 2017, 10:49pm UTC](https://discuss.elastic.co/t/net-client-and-corefx-lab/70761/4 "2017-01-09T22:49:28Z")

</div>

It's private right now, only because it's in real flux and it might not go anywhere 😄 I'll see if we can open it up with a "here be dragons" caveat

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 6, 2017, 10:49pm UTC](https://discuss.elastic.co/t/net-client-and-corefx-lab/70761/5 "2017-02-06T22:49:50Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.