Hi Randy,
As Mike said, no downside for retrieval. But the actual posting mechanism
will remain FTP, because we have hundreds of PWG document references
in specs from other standards bodies and those have to be long-term stable.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG IPP WG
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - TCG Embedded Systems Hardcopy SG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusichttp://sites.google.com/site/highnorthinc
mailto:blueroofmusic at gmail.com
Winter 579 Park Place Saline, MI 48176 734-944-0094
Summer PO Box 221 Grand Marais, MI 49839 906-494-2434
On Tue, Oct 22, 2013 at 5:18 AM, Randy Turner <rturner at amalfisystems.com>wrote:
>> The idea here was that it is more interoperable to access documents via
> their http: link than FTP
>> The browser that was "so defective" was Chrome on OS X Mountain Lion
>> It seems reasonable to use a link with the fewest potential problems for
> access - what's the downside of using http?
>> R.
>> On Oct 22, 2013, at 2:08 AM, Ira McDonald <blueroofmusic at gmail.com> wrote:
>> Hi Mike,
>> So is this a new PWG standard practice decision?
>> Only post all new documents w/ HTTP links? Because someone
> has a browser so defective that it can't access FTP links?
>> Sorry, up all night on calls to TCG meeting sessions in Osaka, Japan,
> so I'm a bit frustrated by this thread.
>> Cheers,
> - Ira
>>> Ira McDonald (Musician / Software Architect)
> Chair - Linux Foundation Open Printing WG
> Secretary - IEEE-ISTO Printer Working Group
> Co-Chair - IEEE-ISTO PWG IPP WG
> Co-Chair - TCG Trusted Mobility Solutions WG
> Chair - TCG Embedded Systems Hardcopy SG
> IETF Designated Expert - IPP & Printer MIB
> Blue Roof Music/High North Inc
>http://sites.google.com/site/blueroofmusic>http://sites.google.com/site/highnorthinc> mailto:blueroofmusic at gmail.com> Winter 579 Park Place Saline, MI 48176 734-944-0094
> Summer PO Box 221 Grand Marais, MI 49839 906-494-2434
>>>> On Mon, Oct 21, 2013 at 11:54 PM, Michael Sweet <msweet at apple.com> wrote:
>>> Ira,
>>>> You can now use ftp: or http: to reference files on the FTP server, e.g.:
>>>>ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippsix10-20130923.pdf>>http://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippsix10-20130923.pdf>>>>>> On Oct 21, 2013, at 7:46 PM, Ira McDonald <blueroofmusic at gmail.com>
>> wrote:
>>>> Hi Mike,
>>>> Out of curiosity, since there were a lot of topics in Randy's note,
>> *what* is
>> now done?
>>>> Cheers,
>> - Ira
>>>>>> Ira McDonald (Musician / Software Architect)
>> Chair - Linux Foundation Open Printing WG
>> Secretary - IEEE-ISTO Printer Working Group
>> Co-Chair - IEEE-ISTO PWG IPP WG
>> Co-Chair - TCG Trusted Mobility Solutions WG
>> Chair - TCG Embedded Systems Hardcopy SG
>> IETF Designated Expert - IPP & Printer MIB
>> Blue Roof Music/High North Inc
>>http://sites.google.com/site/blueroofmusic>>http://sites.google.com/site/highnorthinc>> mailto:blueroofmusic at gmail.com>> Winter 579 Park Place Saline, MI 48176 734-944-0094
>> Summer PO Box 221 Grand Marais, MI 49839 906-494-2434
>>>>>>>> On Mon, Oct 21, 2013 at 10:41 PM, Michael Sweet <msweet at apple.com> wrote:
>>>>> This is now done.
>>>>>> On Oct 21, 2013, at 4:40 PM, Randy Turner <rturner at amalfisystems.com>
>>> wrote:
>>>>>> >
>>> > Ok, thanks.
>>> >
>>> > This happened again this evening when I tried to access the links that
>>> Joe Murdock published earlier today…I was using a laptop that was failing
>>> the FTP links.
>>> >
>>> > If we could just substitute http for ftp when publishing links then
>>> this would be great…
>>> >
>>> > R.
>>> >
>>> >
>>> > On Oct 21, 2013, at 7:15 PM, Michael Sweet <msweet at apple.com> wrote:
>>> >
>>> >> Randy,
>>> >>
>>> >> On Oct 21, 2013, at 4:03 PM, Randy Turner <rturner at amalfisystems.com>
>>> wrote:
>>> >>>
>>> >>> Hi Guys,
>>> >>>
>>> >>> I would like to request that hyperlinks to documents (minutes,
>>> documents, whatever) be "http:" links instead of "ftp:" links -- on a
>>> number of occasions, I and some of my colleagues have been in situations
>>> where we are using a browser that has issues with issuing "ftp:" requests.
>>> >>>
>>> >>> Whereas using "http:" requests would be more "universal" with
>>> regards to be able to access documents in any browser context (even at an
>>> internet cafe where we might not have configuration capability with the
>>> browser).
>>> >>
>>> >> We already have (currently undocumented) aliases on the main pwg.orgweb site to the standards directories. It would be trivial to support "
>>>http://ftp.pwg.org/.. <http://ftp.pwg.org/>." aliases for all "
>>>ftp://ftp.pwg.org/.. <ftp://ftp.pwg.org/>." links.
>>> >>
>>> >>> Also, on another topic, after navigating the PWG website, I can't
>>> find any way to subscribe to the "PWG announce" mailing list. I already
>>> subscribe -- I'm making this comment because one of my colleagues was
>>> trying to subscribe and couldn't find a "subscribe" link for "PWG-announce".
>>> >>
>>> >> Anyone that is subscribed to the WG mailing lists automatically
>>> should be subscribed to the pwg-announce list, but you can subscribe to
>>> just the pwg-announce list at:
>>> >>
>>> >> https://www.pwg.org/mailman/listinfo/pwg-announce>>> >>
>>> >> _________________________________________________________
>>> >> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>> >>
>>> >>
>>> >
>>>>>> _________________________________________________________
>>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>>>> _______________________________________________
>>> cloud mailing list
>>>cloud at pwg.org>>>https://www.pwg.org/mailman/listinfo/cloud>>>>>>>>> _________________________________________________________
>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>>>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/cloud/attachments/20131022/581110bb/attachment.html>