Bryce L Nordgren wrote:
> 19119 is what you're after and it is also an OGC doc (Abstract Spec, Topic
> 12; http://portal.opengeospatial.org/files/?artifact_id=1221). As I
> recall, it avoids implementation details like the plague. It does provide
> some suggestions as to how to categorize various
[EMAIL PROTECTED] wrote on 04/22/2008 04:42:10
PM:
>
> > If a standard API exists (ISO, OGC or JCP), I would like to push very
> > hard for using it.
> Finally the question of a standard API; if you have any suggestions I am
> open to them (hence my review of Future/Executor/Callable).
>
> Other
> If a standard API exists (ISO, OGC or JCP), I would like to push very
> hard for using it.
Finally the question of a standard API; if you have any suggestions I am
open to them (hence my review of Future/Executor/Callable).
Other things to review:
- ISO - I cannot review ISO standards; pay t
Hi Martin this is not proving an effective use of either of our time; I
am not sure you understand the design of Executor/Callable/Future. Many
of your questions seem focused on the technicalities of stopping a
process; rather than the responsibilities and relationships of the
objects involved.
Going to reply to this in multiple parts; since we have a large email
here and many points we agree on.
Martin Desruisseaux wrote:
> Runnable or Callable can be extended with a cancel() method. This is
> what I'm pushing for. I have the feeling that our disagreement come
> from the fact that the
Jody Garnett a écrit :
> Thread and Runnable are a good base, but the design suffers from some
> serious flaws with respect to canceling a running Thread.
Runnable or Callable can be extended with a cancel() method. This is what I'm
pushing for. I have the feeling that our disagreement come from
Martin Desruisseaux wrote:
> It still not clear to we why the Process interface needs to be
> unrelated to standard Java API like Callable?
Hi Martin;
I have been having a hard time communicating this one. I think we are
both looking at the same code and seeing different things.
We have three
ArcGrid ASCII format malfunction (AsciiGridsImageMetadata malfunction)
--
Key: GEOT-1781
URL: http://jira.codehaus.org/browse/GEOT-1781
Project: GeoTools
Issue Type: Bug
Adrian Custer a écrit :
> Are you planning to write up a proposal to how this work can be
> integrated into geotools? If so, what's the timeframe for that work?
>
> --adrian
>
> On Tue, Apr 22, 2008 at 10:49 AM, johann sorel <[EMAIL PROTECTED]> wrote:
>
>> hello,
>>
>> I commited OGC SE in Geo
Are you planning to write up a proposal to how this work can be
integrated into geotools? If so, what's the timeframe for that work?
--adrian
On Tue, Apr 22, 2008 at 10:49 AM, johann sorel <[EMAIL PROTECTED]> wrote:
>
> hello,
>
> I commited OGC SE in GeoAPI,
> those interested (I guess jody a
hello,
I commited OGC SE in GeoAPI,
those interested (I guess jody and simone) can now review.
--
Johann Sorel
Company - Geomatys GIS Developer
Mail - [EMAIL PROTECTED]
-
This SF.net email is sponsored by the 2008 JavaOn
It still not clear to we why the Process interface needs to be unrelated to
standard Java API like Callable? Why the following can't work?
public interface Process extends Callable {
void addListener(ProgressListener);
void removeListener(ProgressListener);
void cancel();
}
Keep
Plugins coming from the parent pom (maven 2.0.9) can be removed in the pom.xml
--
Key: GEOT-1780
URL: http://jira.codehaus.org/browse/GEOT-1780
Project: GeoTools
Iss
13 matches
Mail list logo
