From: <pao...@am...> - 2005-11-29 18:01:20
|
What about providing a default SRS value server-wide??? Something inside the config of GeoServer. I think most people will only use the very same SRS for all their tables, so a server-wide value should save client code most of the time. Bye Paolo Rizzi > -----Messaggio originale----- > Da: Gabriel Rold=C3=A1n [mailto:gr...@ax...] > Inviato: marted=C3=AC 29 novembre 2005 19.54 > A: geo...@li... > Cc: Brent Owens; Justin Deoliveira; David Blasby > Oggetto: Re: [Geoserver-devel] Re: about SRS parameter >=20 >=20 > Agreed, we can schedule it for after 1.3.0. >=20 > Anyway, note the current behavior is to let it null, not to=20 > use 4326, so I'm=20 > letting it as is, which finally means querying in whatever=20 > the feature source=20 > is in. > Problem is when more than one FS is being queries at the same=20 > time, though. >=20 > comments? >=20 > On Tuesday 29 November 2005 18:48, Brent Owens wrote: > > If we do make this manditory, do we want it for 1.3.0? > > > > We can always make it pseudo optional. If the SRS is supplie din = the > > request, we use it. If it is not supplied, we add in 4326=20 > as a default. > > This will stop client code from breaking. This could result in > > unexpected results however. > > > > I think we need to look at how long it would take to change, and = how > > many other things it will break, in order to determine when=20 > we should > > implement it. > > > > Brent Owens > > TOPP > > > > Justin Deoliveira wrote: > > > I guess my only concern is that making the SRS parameter = manditory > > > breaks client code that doesn't presently supply the=20 > paramter. Making > > > things optional is much easier then making things mandatory. > > > > > > On the other hand the spec saying it should be manditory=20 > is big hammer > > > to throw around. > > > > > > What does everyone else think. > > > > > > -Justin > > > > > > Gabriel Rold=C3=A1n wrote: > > >> Hi all, > > >> > > >> I just created http://jira.codehaus.org/browse/GEOS-493 > > >> > > >> the question is if you're ok in making SRS parameter mandatory > > >> (that's what the spec says). > > >> > > >> Cheers, > > >> > > >> Gabriel. > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep=20 > through log > > files for problems? Stop! Download the new AJAX search=20 > engine that makes > > searching your log files as easy as surfing the web. =20 > DOWNLOAD SPLUNK! > > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > > _______________________________________________ > > Geoserver-devel mailing list > > Geo...@li... > > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep=20 > through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. =20 > DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dclick > _______________________________________________ > Geoserver-devel mailing list > Geo...@li... > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >=20 AVVERTENZE AI SENSI DEL D. LGS. 196/2003 =20 Le informazioni contenute in questo messaggio di posta elettronica e/o = nel/i file/s allegato/i, sono da considerarsi strettamente riservate. Il loro utilizzo =C3=A8 consentito esclusivamente al destinatario del = messaggio, per le finalit=C3=A0 indicate nel messaggio stesso. Qualora riceveste questo = messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene = notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema; costituisce comportamento contrario = ai principi dettati dal D. Lgs. 196/2003 il trattenere il messaggio = stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalit=C3=A0 diverse. |