I'd like to reopen the discussion about deprecating DynamicRegionFactory. This is some old crufty code I don't think we want anyone to use. I see we had a ticket to deprecated it (GEODE-388), but we chose not to do it because we don't have an alternative API to create regions from the client (GEODE-215).
The thing is, there is a pretty easy workaround to use functions to create regions from the client. Personally I'd recommend that over DynamicRegionFactory. Can we just deprecate DynamicRegionFactory now and implement GEODE-215 later? -Dan
