Re: Using Kgio::TCPSocket.start with EventMachine (in non blocking way)

["Iñaki Baz Castillo" <ibc@aliax.net>]

2012/4/9 Eric Wong <normalperson@yhbt.net>:
> Kgio::TCPSocket.start is correct.  I'm not sure what you need the
> "on_connected" callback for, but you can just do whatever you want
> to do on the initial write.  You can keep track of the initial write
> vs subsequent writes with an instance variable.
>
> Just try writing, and if you get :wait_writable, tell EM to have it
> watch for writability somehow.
>
>
>  sock = Kgio::TCPSocket.start(...)
>  buf = "TEST"
>  case buf = sock.kgio_trywrite(buf)
>  when :wait_writable
>    # Tell EM to wait for sock to be writable
>    # It's been a while since I've used EM
>    # so I'm not familiar with the API anymore.
>  when nil
>    # initial write completed
>
>    # otherwise, keep looping if we have an unwritten string
>    # (we'll probably hit :wait_writable at the next iteration)
>  end while String === buf


Thanks Eric, really useful. Let me just a question:

Could it be some other case in which kgio_trywrite returns != nil
*after* connection has been properly established?


-- 
Iñaki Baz Castillo
<ibc@aliax.net>