ni
Single User Event for multiple gRPC
Currently, you have a separate User Event (UE) for each gRCP call type. This requires a lot of extra "boilerplate" to set up each UE, as shown in this image:
Normally, the value of separate UEs is strong typing, in that each can have a different type. However, here all UEs have the same type, a single U64 that identifies the gRPC specific call. Typedefs are used to convert, with no strong typing. Thus one gains no benefit from all the extra boilerplate.
Instead, consider having only one User Event for all gRPC names, containing a cluster of two things: the U64 gRPC, plus a string containing the RPC name. This single UE then carries all gRPC calls, with the string being fed into a case structure.
Then adding a new gRPC message just involves two message typedefs, a call to RegisterServerEvent (with tha existing UA), and a new frame in the case structure.
Actually, one can get close to what i would like, but combining all the UE into an array, and then looking up the Event Ref in a Map to get the RPC Name. Like this:
I would disagree with this change. I think the ability to handle requests in different event loops may be necessary in many projects so different requests don't block each other (The async version of the current server template)
Handling requests in parallel would be best done using a well rested and capable framework. A user of Actor Framework would use nested actors for parallel handling, for example. However, as long you aren't hindering such users then I don't mind multiple User Events. It can be worked around, as I show in my example.