There are some differences. The Java version has several items that are
very Java centric. There are also some items that probably need to be
implemented in the native clients. Most the other items, like pools,
servers, region, etc. are pretty much the same.
I think it would be worth having a deta
+1 for common point of reference!
On Mon, Jan 23, 2017 at 10:09 AM, Anthony Baker wrote:
> Are there any differences between the client-cache element in Geode vs
> Native XSD? Seems like a really good idea to use a single, common schema.
>
> Anthony
>
> > On Jan 23, 2017, at 10:05 AM, Jacob Bar
Are there any differences between the client-cache element in Geode vs Native
XSD? Seems like a really good idea to use a single, common schema.
Anthony
> On Jan 23, 2017, at 10:05 AM, Jacob Barrett wrote:
>
> Today we have Geode XSD which contains two root elements, cache (server)
> and clie
I think this is a good idea: it reduces an unnecessary and potentially
confusing redundancy.
Sarge
> On 23 Jan, 2017, at 10:05, Jacob Barrett wrote:
>
> Today we have Geode XSD which contains two root elements, cache (server)
> and client-cache and Native XSD that contains a client-cache. For
Today we have Geode XSD which contains two root elements, cache (server)
and client-cache and Native XSD that contains a client-cache. For the most
part these two schemas are the same for element client-cache. It strikes me
that it makes sense to coalesce these into a single common XSD. For areas
t
