Niclas Hedhman wrote: > 1. No code at all depend on Runtime. (Soon this will be done for > bootstrap as well.)
You mean, if you use bootstrap, then you don't need runtime as well (as it used to be)? > 2. As little actual code as possible in API and SPI. Prefer > interfaces over classes. > > 3. No complex instantiation patterns slowing down the 'critical paths'. > > > So, IMHO, if the RDFizer and/or its ModelVisitors needs to cast to the > runtime classes, then the pattern is flawed, and we should fix that. > One part of this 'puzzle' is of course to define what are the formal > structures that goes into the RDF description, as these should be > maintained. True. The same model is needed by the graph visualizer as well, so any SPI considerations for the model holds for the visualizer as well. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
