proposal for common configuration elements for ITAPS services

[Tim Tautges]

One such example from MOAB is the use of ranges, where a large collection of contiguous handles can be stored in 
constant size.  That comes from assumptions a MOAB-based application can make about handle structure that can't be made 
in iMesh apps.

- tim

On 09/20/2010 11:38 PM, Mark Miller wrote:
> On Mon, 2010-09-20 at 21:18, seol at scorec.rpi.edu wrote:
>
>
>>
>> Switching to have --enable-i*** by default would work for SCOREC S/W.
>> However, we didn't have --enable-ixxx by default
>> on purpose since users cannot take full advantage of SCOREC S/W functionalities through ITAPS.
>
> So that may be a reason to recommend use of FMDB internal interfaces
> over ITAPS, depending on the circumstances. But, I don't think its a
> good reason NOT to build the ITAPS interface to begin with.
>
> Out of curiosity, whats an example of something FMDB can do that is NOT
> available through iMesh/iMeshP? And, what was/is the rationale for not
> making it available through iMesh/iMeshP? This is just a curiosity.
>
> Mark
>
>

-- 
================================================================
"You will keep in perfect peace him whose mind is
   steadfast, because he trusts in you."               Isaiah 26:3

              Tim Tautges            Argonne National Laboratory
          (tautges at mcs.anl.gov)      (telecommuting from UW-Madison)
          phone: (608) 263-8485      1500 Engineering Dr.
            fax: (608) 263-4499      Madison, WI 53706