Implementation of gnet Client about gnet HOT 30 CLOSED

The development of the client for gnet has already started, coming soon.

The first stable version will be released within the next two months.

from gnet.

I am focusing on the gnet implementation in server-side currently, so the delivery of client-side might be later.

from gnet.

希望快点开展client的支持，实际应用中会需要多个服务器协同工作，这时候就需要有Server和Client，我在改造的时候也遇到了相同的问题

from gnet.

I wrote a basic TCP client implementation. Seems to be working so far. The basic idea was that a client works pretty much like a server except it doesn't have a listen address. So I pretty much just added a second set of methods for setting up the Client event loop under the Server object (now the name doesn't make sense). Then there is an additional registration step of TCP connections (rather than connections being registered from the listener socket on the server). So you can use the standard golang TCPConn to dial and get the file descriptor from it and then register it to start monitoring for events. This is more of a starting point if anyone is interested.

calbot@0a400d1

EDIT...
Updated so that it uses syscalls instead of net.TCPconn like gnet already does. That fixes disconnect issues.
calbot@b6c453e

from gnet.

Focus on this issue progress...

from gnet.

How does it go?

from gnet.

I plan to start it after a stable server version of gnet is released but gnet server is still under active development, so the implementation of the gnet client won't be delivered in the near future.

from gnet.

有进展吗？

from gnet.

暂时还没开始。

from gnet.

+1

from gnet.

+1

from gnet.

@panjf2000 i am also really interested in the client implementation and it's accompanying performance improvements compared to standard net package. If you could provide some references/guidelines regarding client implementation, i can try and make a PR!

from gnet.

@ALL
Sorry, I've been so stuck with work stuff lately that I don't have time for this in the near future!
So it would be great if someone is willing to devote to the development of gnet client!

@panjf2000 i am also really interested in the client implementation and it's accompanying performance improvements compared to standard net package. If you could provide some references/guidelines regarding client implementation, i can try and make a PR!

Maybe you can refer to the implementation of netty client? After all, I drew on many ideas from netty when I was developing the server framework of gnet. Thank you in advance. @Ice3man543

from gnet.

+1 for client for sure

from gnet.

@lesismal I believe the standard golang TCP library uses events internally except it is serialized to a single goroutine from the API perspective. If you want to load test a server it's very nice to event/non-blocking IO client otherwise you'll quickly run out of memory for all the goroutines. If you want to test thousands or millions of client connections you're going to want to use non-blocking IO/events.

from gnet.

Thanks @lesismal. I already ran my test using the my fork I mentioned above but I starred your repo for next time 😃

from gnet.

有规划了吗？

from gnet.

The development of the client for gnet has already started, coming soon.

The first stable version will be released within the next two months.

期待client的发布，希望功能全面、性能强劲
距离7.20已经1个月了，能透露一下计划是在什么时候发布吗，client支持Windows吗

from gnet.

I was wandering ,if Client will be released in September?

from gnet.

I was wandering ,if Client will be released in September?

Yes.

from gnet.

请问，现在研发进展符合当初预期吗，9月底能否出个可交互版？

from gnet.

目前计划还是这个月底发布 v0.1.0 版本

from gnet.

Will you release the gnet client in this month?

from gnet.

Sorry for the delay, actually the code of the client has been done, but it's still not fully tested, I've been stuck in my daytime job lately.

from gnet.

咨询下client release版本有发布预计日期吗？

from gnet.

I've been stuck with the daytime job and other personal affairs for a really long time.

Therefore, I can't make a guarantee for the release date of gnet client, I expect to have time to work on it by the end of the month and release the first version in December.

from gnet.

如果client还是用net.Dial的话，这就又让runtime去接管epoll了，runtime.netpoll的优先级又比较低，在P繁忙的情况下会有十几ms的延迟。

from gnet.

gnet leverages net.Dial() to get a reliable client socket and then duplicate its underlying fd by dup(), finally call net.Conn.Close() which will remove the original fd from the netpoll of Golang and close it, by then the original fd will have no impact on Go netpoll.

from gnet.

gnet的优势是利用底层网络特性，避免net库的沉重包袱，client为啥要用net.dial还是同步阻塞的呢？用系统调用级非阻塞connect, epoll托管连接状态，基于状态机驱动，比同步阻塞connect效率会高不少吧

from gnet.

hello，Client什么时候支持Windows环境呢？

from gnet.