From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=pass header.i=@apple.com header.s=20180706 header.b=hLNoMfdv; spf=pass (domain: apple.com, ip: 17.171.2.68, mailfrom: afish@apple.com) Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) by groups.io with SMTP; Wed, 04 Sep 2019 17:35:44 -0700 Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id x850W0U0013597; Wed, 4 Sep 2019 17:35:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=sender : from : content-type : mime-version : subject : date : references : to : in-reply-to : message-id; s=20180706; bh=SXHdNMS8FT6d0B1wQ8AhxtTicEA9AOjrun7d7y9Mk3A=; b=hLNoMfdv4VK5O+zerpx2Nb9AVZK3wiKo2so7uma7qudBvwSU+5T0vpJj7PZfz6ZNo+Zr Trl8AKCC/viegO8xBBTbqVXj2tyXYa5wZCbhIjbnjvaxdwEt4cyfZLjHAUuapttsgne1 I2Q+VkWYKjLMLGrsUwR4W5LYafrYrkVhYRTzsglFGgcCpnXYH7loY/dlGCVX0WDodW65 WAFkmcHHaURCCp+phJcanLwzNljQrSIpW16FNo5r2dXAyPoaqzWaWYIswBORzXV4gsKO +f80wM/N2I1LsO2OplFW7BgiJirepaQHxl+s1IuVLqYtXHcAF9ETlGheRvuG2GyH3Crc wQ== Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 2uqnk4gr2y-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 04 Sep 2019 17:35:42 -0700 Received: from nwk-mmpp-sz11.apple.com (nwk-mmpp-sz11.apple.com [17.128.115.155]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPS id <0PXC00GPB1NG0M30@ma1-mtap-s01.corp.apple.com>; Wed, 04 Sep 2019 17:35:42 -0700 (PDT) Received: from process_milters-daemon.nwk-mmpp-sz11.apple.com by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) id <0PXC008001NHZ900@nwk-mmpp-sz11.apple.com>; Wed, 04 Sep 2019 17:35:42 -0700 (PDT) X-Va-A: X-Va-T-CD: fc4de0ab1b28b90c1989f0db93b04441 X-Va-E-CD: 3f69c98d0f6aac1ea45a962e8f5df907 X-Va-R-CD: 7b06f41ea370f1a19540e4fd5050fcd1 X-Va-CD: 0 X-Va-ID: 64ebb29b-2712-4455-82e0-9e89be855388 X-V-A: X-V-T-CD: fc4de0ab1b28b90c1989f0db93b04441 X-V-E-CD: 3f69c98d0f6aac1ea45a962e8f5df907 X-V-R-CD: 7b06f41ea370f1a19540e4fd5050fcd1 X-V-CD: 0 X-V-ID: d2bdc6d3-a208-4b54-9500-b262c368f187 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-09-04_06:,, signatures=0 Received: from [17.235.44.2] (unknown [17.235.44.2]) by nwk-mmpp-sz11.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPSA id <0PXC001KB1N38IF0@nwk-mmpp-sz11.apple.com>; Wed, 04 Sep 2019 17:35:30 -0700 (PDT) Sender: afish@apple.com From: "Andrew Fish" MIME-version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: [edk2-devel] Mappings and StdLib Date: Wed, 04 Sep 2019 17:35:16 -0700 References: <01d101d5637e$e80098c0$b801ca40$@insyde.com> To: devel@edk2.groups.io, tim.lewis@insyde.com In-reply-to: <01d101d5637e$e80098c0$b801ca40$@insyde.com> Message-id: X-Mailer: Apple Mail (2.3445.104.11) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-09-04_06:,, signatures=0 Content-type: multipart/alternative; boundary="Apple-Mail=_AA16C189-BBE9-459D-A320-AC2850CCFA64" --Apple-Mail=_AA16C189-BBE9-459D-A320-AC2850CCFA64 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Tim, I don't know about the plans with the StdLib, but I do remember a long tim= e ago with the old shell there was a protocol that let you translate volume= names (mappings) into handles and device paths.=20 So you could write a simple library that has 2 styles of APIs: 1) Handle + FilePath in Shell mapping with Volume Name out 2) Shell file path with mapping Volume names in and Simple File System han= dle Out with the file path a) A device path out version of this is also useful You can make the lib just error return if the Shell protocol does not exis= t so you don't make it a requirement. The caller handles that failure as th= e current working volume/directory case.=20 Thanks, Andrew Fish > On Sep 4, 2019, at 5:14 PM, Tim Lewis wrote: >=20 > Following up on my last e-mail, I guess I had the wrong assumption: ther= e doesn=E2=80=99t appear to be a way to resolve mappings within StdLib. > > Are there any plans here? > > Thanks, > > Tim >=20 --Apple-Mail=_AA16C189-BBE9-459D-A320-AC2850CCFA64 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Tim,

I don't know about the plans with the StdLi= b, but I do remember a long time ago with the old shell there was a protoco= l that let you translate volume names (mappings) into handles and device pa= ths. 

So you= could write a simple library that has 2 styles of APIs:
1) Handle + FilePath in Shell mapping with Volume Name out
2) Shell file path with mapping Volume names in and Simple File Sys= tem handle Out with the file path
a) A device path out version o= f this is also useful

You can make the lib just error return if the Shell protocol does no= t exist so you don't make it a requirement. The caller handles that failure= as the current working volume/directory case. 
<= br class=3D"">
Thanks,

Andrew Fish

=
On Sep 4, 2019, at 5:1= 4 PM, Tim Lewis <tim.= lewis@insyde.com> wrote:

Following up on my last e-mail, = I guess I had the wrong assumption: there doesn=E2=80=99t appear to be a wa= y to resolve mappings within StdLib.
 
Are there any plans here?
 
= Thanks,
 
Tim

--Apple-Mail=_AA16C189-BBE9-459D-A320-AC2850CCFA64--