-
Notifications
You must be signed in to change notification settings - Fork 111
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
select & mono - The requested feature is not implemented. #22
Comments
removed the select call but still getting more errors;
I was able to use CSRedis with mono with this commit - https://github.com/ctstone/csredis/tree/6667063d156bf04673449996b4f3560918631c4c but seems a change after broke it. |
The latest releases use SocketAsyncEventArgs for faster async On Tue, Sep 2, 2014 at 11:18 AM, Hüseyin Uslu notifications@github.com
|
What version/platform of Mono are you using? I am able to run Select() and Auth() using Mono for Windows 3.2.3 and build 3.2.1 of csredis. Do you have a full stack trace? |
Ok, I have repro'd on a Linux VM. Here is the offending stack:
Here is the EndPoint.Serialize() definition, and it is indeed undefined: CSRedis uses a DnsEndpoint which does not override base EndPoint.Serialize(): Mono's Socket.Connect() appears to correctly handle IPEndPoint, which does implement Serialize: Here is the originating Connect() call: |
what's your mono version? |
Is there any fix on your mind? csredis is the only c# redis package that was able to run on linux/mono. |
You can try the Develop branch using your own EndPoint (specifically, an IPEndPoint):
Not quite ready to push these changes to the Master branch, but I'm curious to know if this workaround works for you. |
getting this with develop branch;
|
@ctstone , yes endpoint fix worked;
|
fwiw still had this issue on mono 4.2.1. workaround fixed it beautifully, thx. |
Using csredis with mono.
Using sync client - and select command
Getting;
any ideas?
The text was updated successfully, but these errors were encountered: