>
>
> On Tue, Jan 10, 2017 at 7:39 AM Andrea Aime <[email protected]>
> wrote:
>
>> On Mon, Jan 9, 2017 at 11:51 PM, Jody Garnett <[email protected]>
>> wrote:
>>
>>
>> 1. Switch REST API to Spring MVC
>>
>> I think this represents the largest pain for for our user community in
>> the mix - +1
>>
>>
>> Yeah, lots of tickets, but most complaining about functionality, not the
>> library stuff has been implemented with.
>> Searching for REST: https://osgeo-org.atlassian.net/issues/?jql=
>> project%20%3D%20GEOS%20AND%20status%20%3D%20Open%20AND%
>> 20component%20%3D%20REST
>> Searching for the module (not always properly assigned):
>> https://osgeo-org.atlassian.net/issues/?jql=project%20%3D%20GEOS%20AND%
>> 20status%20%3D%20Open%20AND%20component%20%3D%20REST
>>
>> My main fear is that we'd be spending the week doing a library switch and
>> leave that pile untouched, if not grown due to behavior changes in the
>> switch.
>>
>>
> Even if we only manage to pull off a library switch, I feel like that
would be beneficial in making it easier to implement various
requested/broken functionality. From my experience with Spring MVC, it is
much nicer to use and modify than what we are currently using.
Torben
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
