[PATCH] add documentation about backend naming for VMOD authors

[Poul-Henning Kamp]

--------
In message <CABoVN9AGEsQCJxso4bZX41gda8yf+nOm9wEaoiLAqwRMaT=TbQ at mail.gmail.com>, Dridi Bouke
lmoune writes:

>> The way we solve that problem in kernels is to name the VCL_HasBackend()
>> function VCL_CreateBackend() and allowing it to fail :-)
>
>Why not keep VRT_new_backend as the only interface for VMODs and allow
>this one to fail? (or do the atomic auto-renaming if needed)

That may be the eventual outcome, but first we have to figure out
how we want this to work, before we can decide how to make it work
that way.

>It occurred to me today that I was replying with 4.1 in mind and that
>it may not be the case for you.

I'm trying to think of a way to make 4.1 not be a dead end.  I would
far prefer that whatever we do to 4.1, it points directly at, rather
than away from 5.0.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.