Re: Strange nntp port number?

[Lars Magne Ingebrigtsen <larsi@ifi.uio.no>]

Kai Grossjohann <grossjoh@ls6.informatik.uni-dortmund.de> writes:

> I have learned from inspecting nndir.el that I should write a function
> nndb-execute-nntp-command which calls the nntp-functions, then use
> this to redirect all nntp-* functions.
> 
> Right now, this is what nndb-execute-nntp-command looks like:
> 
>     (defun nndb-execute-nntp-command (command)
>       (let ((nntp-port-number nndb-port-number)
>             (nntp-address nndb-address))
>         (eval command)))

I think something like the following might do the trick:

     (defun nndb-execute-nntp-command (command)
       (unless (nntp-server-opened nndb-current-server)
	 (nntp-open-server nndb-current-server 
			   `((nntp-port-number ,nndb-port-number)
			     (nntp-address ,nndb-address))))
       (eval command))

The backend thing feels kinda kludgy.  Perhaps I should think more
OO-y thoughts and implement some kind of inheretance scheme.  It's
just loose thoughts at the moment, but perhaps one should be able to
say something like:

(nnheader-inherit 'nntp 'nndb)

This would define all nndb interface functions as the nntp functions,
but with a wrapper like the one above around each function call.  That
means that one should have a:

(nnheader-define-server 'nndb
  `((nntp-port-number ,nndb-port-number)
    (nntp-address ,nndb-address)))

That defines the mapping from nndb variables to nntp variables.

Hm.  But one should be able to inherit functions from several
backends.  (nndir uses both nnml and nnmh functions, for instance.)

(defun nndb-request-article (&rest args)
  (nnheader-call-function 'nntp 'nndb args))

Hm.  Then one neeps several mappings like the define-server call
above...   

These are all rather easy to implement.  Perhaps we should think some
more and come up with a totally new backend interface scheme.  Any
ideas? 

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."