Re: Asynchronous DNS

[Lars Ingebrigtsen]

Lars Ingebrigtsen <address@hidden> writes:

> It would be better if the application code didn't have to care, but that
> means that either all those functions will have to block (getting us
> back to square one, basically), or they'll have to set up a queue of
> pending actions to be taken, which I think is rather too ambitious. 

And, by the way, as I think I've said before: The following code will
give a backtrace today:

         (setq proc (make-network-process :name "foo"
                                     :buffer (generate-new-buffer "*foo*")
                                     :host "localhost"
                                     :nowait t
                                     :service port)))
  (process-send-string proc "echo bar")

with

Process foo not running

because it's still in 'connect.

For even more asynchronicity in the :nowait 'immediate case, there are
other functions that will also fail, like set-process-coding-system,
that do not fail with :nowait t.  And I think that's fine.  When you're
doing async programming, you have to adhere to the rules provided by the
asynchronous sockets, and that you've explicitly asked for.

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