-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 11/02/2015 09:03 AM, Poul-Henning Kamp wrote: > >> So unless we add a requirement like "you have to call >> VCL_Something() to 'register' the director/backend", so that >> VCL_Something() can change the name, I don't think we can use >> suffixes or anything else to enforce unique names. (And as of >> now, I don't see why a VMOD backend wouldn't work even if it >> doesn't call VCL_Something().) > > I think there is merit to this, in the sense that I can see why a > VMOD creating dynamic backends wouldn't want them to "pollute" the > CLI and VSM. > > But in the case where the VMOD wants the backend to appear in the > CLI/VSM, I think it is perfectly fair to disambiguate the name > there, and I think it would be silly to fail the registration, > because some other VMOD happened to use the same name already.
Hmm, I brought up that idea to be dismissive of it, but now I'm beginning to see the merits as well. So we could have something like: VCL_Register(vcl, director) ... which would do things for you like change the name for uniqueness if necessary, create the VBE stats ... (and whatever else we'd offer to do the right way on behalf of director/backend VMODs). And then the docs can say, "Dear VMOD author, you can call that and then we'll take care of these things for you. Or don't, but then you're on your own, just be aware of the consequences." I'm starting to like it. 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJWNzBtAAoJEOUwvh9pJNURfgAP/2v6cf/qg92WYWuWPK6nxDrz iTLkYX0Upaf9fjQ3GI8mZ7Hmzt+mYHdIWUohSxSfatsH1/8nmw2HVtI15r4mtHuv C4Sd+66EGom2tBvVg4BCw1d+snI5WcIEF646taZI3AHWPQ4qKJng2+XKgJU/C8iD kGLh4oM0zh2wxRkouUfx3O5efxQ9v7/Bplv+p0YSXNG+Bo5B5U/Mj0jMbAOKExmu EekQBZA93DYUyBLEH0wNmD7QMruqcCS7QgOfnvTejQR/EN+ThHrxWNyChjy6fWzv sqJ42kW0Wkhis4Eel4ik4jufeCV80zaWrXZoPzBluQXPaFTs88WJjNq0dyK3VFUT Eb5pydCxMDk0y59xDHJD4oL/Y2Ed09rqzdZDg2AKAH6DSehsdp2gcMrB8GEmOk+q gdJBzgCzUSEhbmQTc2kEHbswnLxDTJGbQGj7upMRCUCdmX8p27LlLyYYyFg1aA4i UWJ6y5JQ/YuIR1HvjK2X+4iNKfawydtjZ0tBW5qyId/RHaN6PKEvQhTb0aqiqMXZ IOX2NXtQcYKIs6AKtHzu2yDh0I6IRLdRhmVDewVZc8BW6TmPPO3wpieOmVR3f2fu BlIm7T4ideqk6PBB+YxfzTMKDep9p2xauSjnjqy02ozB6DkjeMVfwjckoQf86jgm cRdzjcB12SRK3PttWxZr =QcUr -----END PGP SIGNATURE----- _______________________________________________ varnish-dev mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
