Re: Asynchronous DNS

[Lars Ingebrigtsen]

With the latest blockers implemented with some added debugging code,

(eww "https://en.wikipedia.org/wiki/Ocelot";)

gives this output:

Async DNS for 'en.wikipedia.org'
Waiting for socket from set-process-filter...
Waiting for socket from set-process-filter...
Async DNS for 'upload.wikimedia.org'
Waiting for socket from set-process-filter...
Async DNS for 'upload.wikimedia.org'
Waiting for socket from set-process-filter...
Async DNS for 'upload.wikimedia.org'
Waiting for socket from set-process-filter...
Async DNS for 'upload.wikimedia.org'
Waiting for socket from set-process-filter...
Async DNS for 'upload.wikimedia.org'
Waiting for socket from set-process-filter...
Async DNS for 'upload.wikimedia.org'
Waiting for socket from set-process-filter...
Waiting for socket from set-process-filter...
Async DNS for 'en.wikipedia.org'
Waiting for socket from set-process-filter...
Waiting for socket from set-process-filter...

Does that function really have to wait for a socket?

It has code like

  if (p->infd >= 0)
    {
      if (EQ (filter, Qt) && !EQ (p->status, Qlisten))
        {
          FD_CLR (p->infd, &input_wait_mask);
          FD_CLR (p->infd, &non_keyboard_wait_mask);
        }
      else if (EQ (p->filter, Qt)
               /* Network or serial process not stopped:  */
               && !EQ (p->command, Qt))
        {
          FD_SET (p->infd, &input_wait_mask);
          FD_SET (p->infd, &non_keyboard_wait_mask);
        }
    }

but I don't think that makes much of a difference...  hm...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no