[PATCH] add documentation about backend naming for VMOD authors

[Geoff Simmons]

On 10/28/2015 09:17 AM, Poul-Henning Kamp wrote:
> 
>> Maybe add a sentence or two to the "Writing a Director" doc about
>> backend names, what they're used for, and why this could be a problem.
> 
> Also a good idea.
> 
> I'm starting to think that maybe we should have a "name-spaces"
> section in the reference manual for stuff like this.

This patch just adds a section to the "Writing a Director" doc about
backend names, and it turned out to be several paragraphs, maybe too
long-winded. Suggestions for editing are welcome.

Or we could move it out to a more comprehensive doc about namespaces,
but that will take some work (and I'm not sure what all it would have to
cover).


Best,
Geoff
-- 
** * * UPLEX - Nils Goroll Systemoptimierung

Scheffelstraße 32
22301 Hamburg

Tel +49 40 2880 5731
Mob +49 176 636 90917
Fax +49 40 42949753

http://uplex.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-add-documentation-about-backend-naming-for-VMOD-auth.patch
Type: text/x-patch
Size: 3846 bytes
Desc: not available
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20151101/c54266ff/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20151101/c54266ff/attachment.pgp>