PengZheng commented on PR #782: URL: https://github.com/apache/celix/pull/782#issuecomment-2603461192
> A remote call is less trustworthy, so IMO crashing (assert fail) is then not an option. I totally agree. > To be honest, I am still unsure if the current array list implementation is the correct approach. Another option could be to really split up the public array list API in a long, double, string, pointer, boolean, version array. So something like: celix_long_array_list_t with functions like celix_longArrayList_get, etc. Imagine that we are dealing with json rather than array list or properties, there are at least two options: 1. Let the service implementation perform type checking manually, calling `json_is_array` etc. 2. Delegate type checking to the framework via json schema, which is essentially the same as type annotation approach. Then it will be OK to add various type assertions to the service implementation, which may be remote or local. Both should work for either local service or remote service. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@celix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
