Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple connections use single CopyingByteBufferAllocator instances? #18

Open
beetlex-io opened this issue Jun 16, 2017 · 1 comment
Open

Comments

@beetlex-io
Copy link

beetlex-io commented Jun 16, 2017

UVStream

ByteBufferAllocatorBase allocator;
public ByteBufferAllocatorBase ByteBufferAllocator
{
get
{
return allocator ?? Loop.ByteBufferAllocator;
}
set
{
allocator = value;
}
}
public void Resume()
{
CheckDisposed();
int r = uv_read_start(NativeHandle, ByteBufferAllocator.AllocCallback, read_cb);
Ensure.Success(r);
}

@txdv
Copy link
Owner

txdv commented Jul 7, 2017

Yeah they do, you can assign your own bytebufferallocator, for every handler and loop.

This one just creates a new buffer and copies the contents to it, so everyone can use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants