From: Jody G. <jga...@re...> - 2006-08-16 09:09:28
|
Hey Cory, Now that I have gone over the page I can have some useful feedback. It seems most of the confusion was in the IRC meeting. I have added a bit of text to the proposal talking about the motivation for the proposal. But I think it is time to ask Andrea for some feedback on the IssueList interface itself, since the API is used for Spring Remoting we need to think about "deep" or "shallow" copy issues. You have this mostly covered with the list of issues (ie shallow) vs individual issue (deep) accessor methods. Andrea is there any "traditional" naming conventions we should be following here? Can you run over the page and provide us with feedback? The only one I can spot right now is the use of a long ID rather then a string, and some note about the horrible equals method implementation needed for remote api use. Cheers, Jody > Hi guys, > > As per the GeoServer Improvement Proposal guidelines, Richard, Pablo, > and myself are proposing a module to provide a client service for a > shared issues list. An "issue" can be a task or geographical feature > which requires attention, but other uses are possible too. uDig will be > taking advantage of this service very soon. The implementation will use > hibernate to back the list onto a database. Some preliminary details > are available (and will be expanded) here: > > http://docs.codehaus.org/display/GEOS/GSIP+3+-+Issues+List+Module > > Comments and questions are welcome. > > Cheers, > Cory. > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Geoserver-devel mailing list > Geo...@li... > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > |