Re: Allowing for remote servers and such.

Leslie Hart (hart@nipmuc.fsl.noaa.gov)
Sun, 15 Sep 1996 14:49:25 -0600 (MDT)

The idea is that a vendor of MPI I/O can supply a series of services, BUT
ALSO any developer can attach services at run-time with the calls outlined.
If we at NOAA/FSL wanted to attach a compression technique to MPI I/O:

Create: "fsl_grib"
Add: only add open, close, and write
(User supplied functions for open, write, and close)

Open file name: "fsl_grib:RUC_40KM:robin.fsl.noaa.gov:nimbus"

Sorry, I am preparing to travel. I can provide a more complete
example when I return.
>
> Thanks for the proposal.
> I like the idea of specifying the service by modifying the filename in
> an implementation-dependent way.
> I'm wondering if that itself would take care of the problem?
> For example, if the filename is prefixed with the service name and
> whatever other information is needed for remote access,
> the MPI_Open routine could interpret that information and internally
> call the equivalent of MPI_Io_create_service, etc., transparent to the
> user. Does the user really need to explicitly call MPI_Io_create_service,
> MPI_Io_add_service, MPI_Io_make_file_handle? Maybe I am missing
> something, so a simple example showing how they are used would be very
> helpful.
>
> Rajeev
>
>