[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mailman-developers
Subject:    Re: [Mailman-Developers] Handling additions to REST API in client side
From:       Barry Warsaw <barry () list ! org>
Date:       2017-12-29 15:10:35
Message-ID: B2431271-4543-4C1D-BD85-7DAF5EA8BA26 () list ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Dec 28, 2017, at 19:50, Abhilash Raj <maxking@asynchronous.in> wrote:

> PATCH won't fail when running partial updates, but it won't silently drop the
> attributes that it doesn't support. So from client side, there is no real way to
> understand when to include that attribute which was added in a later version.

Yes, I see the problem with that.

> We need some way to associate attributes with a minimum Core version, which we
> can get from `/system` endpoint. Although, for now, it probably is an overkill.
> I will do some static stuff to take care of this.

What happens when someone runs from say git head though?  /system/version won't keep \
up with that, and besides, it's going to become an increasingly big compatibility \
matrix over time.

> How bad do you think would it be for Core to silently drop extra attributes and
> only use the ones that it needs?

I think it could be problematic, as Steve points out.

I don't really have a good answer, and I'm wondering what the state of the art is.  \
Maybe we should ask some experts for advice (we do have some friends who are experts \
in this).

-Barry


["signature.asc" (signature.asc)]

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEhBcVftvnPZ6sHlObEm61Y6dLBr8FAlpGWuoACgkQEm61Y6dL
Br/PMw//T8/b/m8Ne3sFG26Jjy/t0q1oBFcVSFvtZnVPWCUb21mIXwjMfye6pwlg
p3W1jL/CLgPPaZ+txRbVOrXCqZvJ74pe/jTEKb7xp7kWigmTaQer7O0lVO6jkbU8
LTgC6dHk4ydCTZc68x2wFtY6zqBncX1uryP19lE6tcCkbDxweKiWwlsF4zGUZlJS
XIPZYRgDwSNRugAqhxG5lzW26F1snS62kIjz2+/C9bqbOenG9c54S49X24rVJSCf
P3q8Zqdgpd34NozD/1+dFVpkva2zoPrEXo0V3TS+Ex7p2b4v3M8jutLpQGSSVnAF
uOLhjCbV11PhW0/peIcX3kKvf66ysjh3/9QWXq23bTNuGlHbsJtLV5D2XjHlQ84I
AXXzU4UpPQIv8RDQmEIHYxmNYqvfHZ3GVZ1yNBpJqcI97ODo5I4+iIndyZkN/tJ6
C3CHP5wcaVvKOMIOhjrTf9sIpUQ8nilyEEaSMq84XgzpobmlLJlkKN51CjXLEOEF
HK9H/T+lJ/CzfRRIiBRml4JCZtvl9+QBmo0YabfeNww6ctFpxACo3jqPX30xaj09
Zfm3QtIFcVh0ZZfDpw4KXJb9e0oVuc3wWbIzxd6bWd+JMe3ehsichu/PDmdwWYRz
na42hWwV3oJO9SUXm677sQYIDduMF7s/YlzGS29ayUUv2Jzhsag=
=gvte
-----END PGP SIGNATURE-----


_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
https://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/mailman-developers%40progressive-comp.com


Security Policy: http://wiki.list.org/x/QIA9



[prev in list] [next in list] [prev in thread] [next in thread]