Austin Eng dc7971ce58 dawn_wire: Support deserializing s->c chained structs ... Chained structs *may* contain objects which means deserialization may need an ObjectIdResolver. However, in practice, we never need to send chained structs from the server to the client that contain objects for a valid command. The one upcoming need for chained server->client structs is to serialize limit structs. Because limit structs never need objects, we provide a dummy implementation of the ObjectIdResolver which always yields an error. An analogous change is done for ObjectIdProvider. These classes will be used in a follow-up CL. Bug: dawn:685 Change-Id: I1c0f3f2d080377f2e1a77bc6e896f24d3d9ab931 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/63981 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>		2021-09-10 20:36:20 +00:00
..
ApiObjects.h	Remove storage class specifier for the explicit template specialization	2020-11-20 09:38:56 +00:00
ApiProcs.cpp	Nuke the ClientMatches hack for same-device validation	2021-02-05 21:08:44 +00:00
ClientBase.h	dawn_wire: Support deserializing s->c chained structs	2021-09-10 20:36:20 +00:00
ClientHandlers.cpp	dawn_wire: Move BufferConsumer to it's own file. Unify WIRE_TRY	2021-02-25 20:21:25 +00:00
ClientPrototypes.inc	dawn_wire: Harden deserialization routines	2021-02-18 19:28:29 +00:00