Re: Adding asynchronous name resolution to GlibC (was: Reproposed F19 Feature: Fix Network Name Resolution)

2013-01-18 Thread Kamil Dudka
On Friday, January 18, 2013 23:35:24 Lennart Poettering wrote: > On Fri, 18.01.13 22:49, Andreas Tunek (andreas.tu...@gmail.com) wrote: > > I think you have a good point, but adding every imaginable featw into > > glibc > > is not really a good solution. Maybe glib is a better place for these > > k

Re: Adding asynchronous name resolution to GlibC (was: Reproposed F19 Feature: Fix Network Name Resolution)

2013-01-18 Thread Lennart Poettering
On Fri, 18.01.13 22:49, Andreas Tunek (andreas.tu...@gmail.com) wrote: > I think you have a good point, but adding every imaginable featw into glibc > is not really a good solution. Maybe glib is a better place for these kinds > of functions? Because doing this externally is really hard. I wrote

Re: Adding asynchronous name resolution to GlibC (was: Reproposed F19 Feature: Fix Network Name Resolution)

2013-01-18 Thread Simo Sorce
On Fri, 2013-01-18 at 22:49 +0100, Andreas Tunek wrote: > > On Jan 18, 2013 8:48 PM, "Lennart Poettering" > wrote: > > > > On Fri, 18.01.13 20:20, Björn Persson (bjorn@rombobjörn.se) wrote: > > > > > If your functions get added to GlibC, then they will only be > available > > > in GNU systems (un

Re: Adding asynchronous name resolution to GlibC (was: Reproposed F19 Feature: Fix Network Name Resolution)

2013-01-18 Thread Adam Jackson
On Fri, 2013-01-18 at 22:49 +0100, Andreas Tunek wrote: > I think you have a good point, but adding every imaginable featw into > glibc is not really a good solution. Maybe glib is a better place for > these kinds of functions? If glibc didn't already have DNS API, that might be a more reasonable

Re: Adding asynchronous name resolution to GlibC (was: Reproposed F19 Feature: Fix Network Name Resolution)

2013-01-18 Thread Colin Walters
On Fri, 2013-01-18 at 22:49 +0100, Andreas Tunek wrote: > Maybe glib is a better place for these kinds of functions? Already exists: http://developer.gnome.org/gio/2.34/GResolver.html -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Adding asynchronous name resolution to GlibC (was: Reproposed F19 Feature: Fix Network Name Resolution)

2013-01-18 Thread Andreas Tunek
On Jan 18, 2013 8:48 PM, "Lennart Poettering" wrote: > > On Fri, 18.01.13 20:20, Björn Persson (bjorn@rombobjörn.se) wrote: > > > If your functions get added to GlibC, then they will only be available > > in GNU systems (unless other vendors decide to clone them) and programs > > that use them wil

Re: Adding asynchronous name resolution to GlibC (was: Reproposed F19 Feature: Fix Network Name Resolution)

2013-01-18 Thread Lennart Poettering
On Fri, 18.01.13 20:20, Björn Persson (bjorn@rombobjörn.se) wrote: > If your functions get added to GlibC, then they will only be available > in GNU systems (unless other vendors decide to clone them) and programs > that use them will be tied to GNU or will need workarounds in their > configuratio

Adding asynchronous name resolution to GlibC (was: Reproposed F19 Feature: Fix Network Name Resolution)

2013-01-18 Thread Björn Persson
Nick Jones wrote: > One feature I would like to see added to future glibc, is a fully > asynchronous version of getaddrinfo, and also getnameinfo. > > Asynchronous for non filesystem fds at least. > > The glibc maintainers don't seem to be against this idea and I am > willing to put time into d