On Thu, Jun 9, 2011 at 6:37 AM, <[email protected]> wrote: > This is more a design question: > > FileWatcher checks for external modifications of a file. But if > tgeoserver code is writing the content of this file itself, how can I > tell the FileWatcher NOT to indicate that the file is modified forcing > an additional reload. > > Proposals > > 1) add a method > > setKnownLastModified(long lastModified) > > 2) add a method > > write(T object) > > which deserializes the object and adjusts the internal last modified > timestamp. > > Proposal 2 has another advantage. It is possible to detect conflicts > if the file was changed externally and internally, throwing a proper > IOException. > > What do you think ?.
The first is probably more generic, does not require a case by case subclass, but I'm wondering if this is an early optimization case. Are the files in question so expensive to reload, or the expected change rate of the file very high? Cheers Andrea -- ------------------------------------------------------- Ing. Andrea Aime GeoSolutions S.A.S. Tech lead Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.youtube.com/user/GeoSolutionsIT http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ------------------------------------------------------- ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
