On Fri, 5 Apr 2019 at 07:29, Andrea Aime <andrea.a...@geo-solutions.it>
wrote:

> Hi,
> while working on the deprecation removal branch I stumbled
> into CachingFeatureSource.... I shared
> that class as an example years ago, was put among library code anyways
> against my suggestion
> and got a deprecation and a warning sounding like "// CachingFeatureSource
> is deprecated as experimental (not yet production ready)".
>
> In these many years nobody made  CachingFeatureSource  production ready,
> so it's time
> to pull the plug on it and remove it. However, documentation refers to it
> via the QuickStartCache example,
> which is one of the first examples users see in the documentation.
>
> I see that there is a SpatialIndexFeatureSource, but there is no "one
> call" way to build it from another feature source.
> This inspires a WTF moment, I'm tempted to just blow away also all the
> documentation affected by the removal....
>
>

It would probably be best if we don't have docs pointing to "immature"
code, it would also be "nice" if we had somewhere to store those sorts of
mostly completed classes that would be useful to future developers coming
along and starting to think about implementing them. For example I have a
mostly working (but would need some additional work for production)
implementation of an updateable map layer that should live some more
visible than my hard drive.

So +1 to remove documentation and unfinished code.  But can anyone think of
a good place to store that sort of code?

Ian



Anyone wants to spend time on a "better" solution?
>
> Cheers
> Andrea
>
>
> == GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf
> Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa
> (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
> http://www.geo-solutions.it http://twitter.com/geosolutions_it
> ------------------------------------------------------- *Con riferimento
> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
> circostanza inerente alla presente email (il suo contenuto, gli eventuali
> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
> sarei comunque grato se potesse darmene notizia. This email is intended
> only for the person or entity to which it is addressed and may contain
> information that is privileged, confidential or otherwise protected from
> disclosure. We remind that - as provided by European Regulation 2016/679
> “GDPR” - copying, dissemination or use of this e-mail or the information
> herein by anyone other than the intended recipient is prohibited. If you
> have received this email by mistake, please notify us immediately by
> telephone or e-mail.*
> _______________________________________________
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>


-- 
Ian Turton
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to