client side caching of element size #12
Description
When a woof is remote, the protocol uses two messages to access it (put or get). The first message gets the element size and the second performs the operation.
Currently there is a cache (based on woof name) to cache this value. The assumption is that it is used in clients that do not persist across subsequent calls to WooFCreate() that could change the element size.
One way to address this issue is to put in some kind of init function for remote access.