Separation of concerns? Big classes which do tons of stuff? Tracing MD5 through all types of classes is also leaking implementation to outsiders etc.
Just 2 cents Michael Am 27.02.2009 5:37 Uhr, schrieb Niclas Hedhman: > On Fri, Feb 27, 2009 at 10:37 AM, Michael Hunger<[email protected]> wrote: >> I looked at the implementation and would like suggest the following to >> reduce the coupling to MD5 and to >> "UnsupportedEncodingExceptions" (and allow different >> SchemaVersionCalculations). >> >> 1) create an interface SchemaVersion >> 2) rename the methods on ValueType etc. to versionize(SchemaVersion) >> 3.1) add such methods on QualifiedName and TypeName (to be created class) >> 3.2) or have SchemaVersion.update(QualifiedName) and updateFrom(TypeName) >> 4) have methods like update(byte[]), byte[] calculage(), String base64() on >> SchemaVersion > > But then we need to store what Schema implementation type with the > entity in the store. If not, then isn't this moot? > > Cheers > Niclas _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
