Hi Everyone,
Perhaps this is a bit premature but I'm pretty excited to be updating RubyDNS.
In order to get to this point, I built a new asynchronous IO framework for Ruby:
`Async::Reactor` implements the reactor pattern and basically takes
all the good parts of `celluloid-io`. The Async gem implements parts
of the async/await pattern - there are a few more things to do but
it's enough now to implement everything I need for RubyDNS.
And on top of that is the core (originally all in RubyDNS)
asynchronous DNS resolver:
This gem provides an asynchronous DNS resolver and server.
Would be great to have feedback, people interested in helping out with
these projects - including documentation, testing, real world usage,
etc.
Kind regards,
Samuel
Greate job man.
No doubt, RubyDNS is most elegant an mature DNS implementation for Ruby
···
On 9 April 2017 at 06:58, Samuel Williams <space.ship.traveller@gmail.com> wrote:
Hi Everyone,
Perhaps this is a bit premature but I'm pretty excited to be updating
RubyDNS.
https://github.com/ioquatix/rubydns
In order to get to this point, I built a new asynchronous IO framework for
Ruby:
https://github.com/socketry/async
`Async::Reactor` implements the reactor pattern and basically takes
all the good parts of `celluloid-io`. The Async gem implements parts
of the async/await pattern - there are a few more things to do but
it's enough now to implement everything I need for RubyDNS.
And on top of that is the core (originally all in RubyDNS)
asynchronous DNS resolver:
https://github.com/socketry/async-dns
This gem provides an asynchronous DNS resolver and server.
Would be great to have feedback, people interested in helping out with
these projects - including documentation, testing, real world usage,
etc.
Kind regards,
Samuel
Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>
--
*Senior Information Security Engineer OSCE, GWAPT, **CEH, **OSCP, **RHCE, *
*CCNA, **MCITP-EA*
I think a DNS server command line is really need for that gem
···
On 9 April 2017 at 10:43, KING SABRI <king.sabri@gmail.com> wrote:
Greate job man.
No doubt, RubyDNS is most elegant an mature DNS implementation for Ruby
On 9 April 2017 at 06:58, Samuel Williams <space.ship.traveller@gmail.com> > wrote:
Hi Everyone,
Perhaps this is a bit premature but I'm pretty excited to be updating
RubyDNS.
https://github.com/ioquatix/rubydns
In order to get to this point, I built a new asynchronous IO framework
for Ruby:
https://github.com/socketry/async
`Async::Reactor` implements the reactor pattern and basically takes
all the good parts of `celluloid-io`. The Async gem implements parts
of the async/await pattern - there are a few more things to do but
it's enough now to implement everything I need for RubyDNS.
And on top of that is the core (originally all in RubyDNS)
asynchronous DNS resolver:
https://github.com/socketry/async-dns
This gem provides an asynchronous DNS resolver and server.
Would be great to have feedback, people interested in helping out with
these projects - including documentation, testing, real world usage,
etc.
Kind regards,
Samuel
Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>
--
*Senior Information Security Engineer OSCE, GWAPT, **CEH, **OSCP, *
*RHCE, **CCNA, **MCITP-EA*
--
*Senior Information Security Engineer OSCE, GWAPT, **CEH, **OSCP, **RHCE, *
*CCNA, **MCITP-EA*
We can implement a command line DNS server. It's pretty simple, let me do it!
···
On 9 April 2017 at 19:45, KING SABRI <king.sabri@gmail.com> wrote:
I think a DNS server command line is really need for that gem
On 9 April 2017 at 10:43, KING SABRI <king.sabri@gmail.com> wrote:
Greate job man.
No doubt, RubyDNS is most elegant an mature DNS implementation for Ruby
On 9 April 2017 at 06:58, Samuel Williams <space.ship.traveller@gmail.com> >> wrote:
Hi Everyone,
Perhaps this is a bit premature but I'm pretty excited to be updating
RubyDNS.
https://github.com/ioquatix/rubydns
In order to get to this point, I built a new asynchronous IO framework
for Ruby:
https://github.com/socketry/async
`Async::Reactor` implements the reactor pattern and basically takes
all the good parts of `celluloid-io`. The Async gem implements parts
of the async/await pattern - there are a few more things to do but
it's enough now to implement everything I need for RubyDNS.
And on top of that is the core (originally all in RubyDNS)
asynchronous DNS resolver:
https://github.com/socketry/async-dns
This gem provides an asynchronous DNS resolver and server.
Would be great to have feedback, people interested in helping out with
these projects - including documentation, testing, real world usage,
etc.
Kind regards,
Samuel
Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>
--
Senior Information Security Engineer
OSCE, GWAPT, CEH, OSCP, RHCE, CCNA, MCITP-EA
--
Senior Information Security Engineer
OSCE, GWAPT, CEH, OSCP, RHCE, CCNA, MCITP-EA
Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk>