Gabriel Roldán wrote: > We have to options. > a) understand the usage of SeTable and SeLayer shall be limited to the bounds > of the runnable. That is, no "client" code shall ever hold a SeTable/Layer on > its own, and we do that as convention since its our module. > Okay I will think about that; I am pretty sure I can do a "mark & sweep". Remember all the SeTable / SeLayers handed to a Runnable and put some safety checks (in the form of an InvalidStateException) if they are used out side of the extent of the Runnable. > b) abstract out the whole ArcSDE API and provide our own facade for the whole > thing > > I though of b) a couple times but never had the energy, nor you'll have on > this run. > > btw, what's your timeframe for this? > I have my first commit ready now; just want to run tests before inflicting it on trunk... it is my top/only priority. Jody
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
