+1
On Jul 31, 2007, at 12:59 PM, Andrea Aime wrote:
> Andrea Aime ha scritto:
>> Hi people,
>> discussion seem to have calmed down.
>> Please vote if you feel like to. 2.4.0-rc0 is not far away.
>
> I updated the page with the last outcomes from the Geoserver
> meeting, and added my vote and Jody
Andrea Aime ha scritto:
> Hi people,
> discussion seem to have calmed down.
> Please vote if you feel like to. 2.4.0-rc0 is not far away.
I updated the page with the last outcomes from the Geoserver
meeting, and added my vote and Jody's one. I think we need
two more for the proposal to pass. Anyon
Hi people,
discussion seem to have calmed down.
Please vote if you feel like to. 2.4.0-rc0 is not far away.
Cheers
Andrea
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? St
I would go with FeatureSource as the "data access side" of the equation.
I am also liking the code examples that are produced when you add it to
FeatureCollection - but golly that class servers too many purposes as it
is :-)
Andrea I am happy either way; want to write up a code example and choo
Justin Deoliveira ha scritto:
> I think I agree with Jody in that you should probably use Hints straight
> up... not because I love the hints api but for reasons of consistency.
Ok, I managed to understand my error, and you are both right. Will
fix the proposal.
> AS for where to put hte honored
Justin Deoliveira ha scritto:
> Andrea Aime wrote:
>> Justin Deoliveira ha scritto:
>>> I think I agree with Jody in that you should probably use Hints
>>> straight up... not because I love the hints api but for reasons of
>>> consistency.
>>>
>>> AS for where to put hte honored hints... not too
Andrea Aime wrote:
> Justin Deoliveira ha scritto:
>> I think I agree with Jody in that you should probably use Hints
>> straight up... not because I love the hints api but for reasons of
>> consistency.
>>
>> AS for where to put hte honored hints... not too sure about that one
>> either. What a
Jesse Eichar ha scritto:
> I like the idea and have wanted this for a while now. But the concern I
> have with this proposal as well as other is getting enough momentum
> behind it to make sure it become real (not just implemented for a single
> datastore and forgotten in a few months).
> My s
Justin Deoliveira ha scritto:
> I think I agree with Jody in that you should probably use Hints straight
> up... not because I love the hints api but for reasons of consistency.
>
> AS for where to put hte honored hints... not too sure about that one
> either. What about throwing another method
I like the idea and have wanted this for a while now. But the
concern I have with this proposal as well as other is getting enough
momentum behind it to make sure it become real (not just implemented
for a single datastore and forgotten in a few months).
My second concern is what is the sta
I think I agree with Jody in that you should probably use Hints straight
up... not because I love the hints api but for reasons of consistency.
AS for where to put hte honored hints... not too sure about that one
either. What about throwing another method on DataStoreFactory for it
called "getQ
Andrea Aime wrote:
>> Then you can perform any number of queries against your FeatureSource.
>> What do you think?
> Dangerous? What if I share the same FeatureSource for some topological
> analisys and some rendering, they do need different hints, and would
> end up stepping on each other toes.
Yo
Jody Garnett ha scritto:
> One alternative idea for you Andrea.
>
> featureSource.setHints( hints );
> Map used featureSource.getImplementationHints();
>
> Then you can perform any number of queries against your FeatureSource.
> What do you think?
Dangerous? What if I share the same FeatureSourc
One alternative idea for you Andrea.
featureSource.setHints( hints );
Map used featureSource.getImplementationHints();
Then you can perform any number of queries against your FeatureSource.
What do you think?
Jody
Andrea Aime wrote:
> Hi,
> turned out I already wrote a Query hint proposal some t
Two things Andrea - create a Jira report (or another page) and put all
the background story and rejected ideas there. Leave the proposal to
stand on its own so people can see the result of all your hard work.
We are also going to need Jesse's review on this one as he is deeply
involved in hacki
Hi,
turned out I already wrote a Query hint proposal some time ago,
and then forgot about it. Today I beefed it up with some extra content,
and it's ready for your commenting pleasure:
http://docs.codehaus.org/display/GEOTOOLS/Add+hints+support+to+Query+object
I think the crux is where to put the
16 matches
Mail list logo
