Groups | Search | Server Info | Login | Register
Groups > comp.os.os2.programmer.misc > #1919
| From | Paul Edwards <mutazilah@gmail.com> |
|---|---|
| Newsgroups | comp.os.os2.programmer.misc |
| Subject | Re: TCP/IP options |
| Date | 2024-03-26 19:53 +0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <utucvv$1pr3j$1@dont-email.me> (permalink) |
| References | <uttrtd$1lrs8$1@dont-email.me> <utu167$1n0oc$1@dont-email.me> <utubss$1piaa$1@dont-email.me> |
And I could even add http://whatever to my PATH, and have Windows or OS/2 binaries there to run. However, there is one thing I need. I currently have links like this: Available <a href="pdoso.zip">here</a>. Ideally I would like a way to distinguish whether this is a text or binary file, thus subject to translation. Is there a way to add that information to that link? Or is this the wrong conceptual place to put that? If it is just treated as a file system - where there is no such distinction normally - and given that an application can choose to open a text file as binary anyway - then perhaps the user is the one who gets to choose whether they want to do a binary download of a link, with no viewing, or open as text, or open as a binary with a particular application that knows how to interpret the binary? BFN. Paul.
Back to comp.os.os2.programmer.misc | Previous | Next — Previous in thread | Next in thread | Find similar
TCP/IP options Paul Edwards <mutazilah@gmail.com> - 2024-03-26 15:02 +0800
Re: TCP/IP options Paul Edwards <mutazilah@gmail.com> - 2024-03-26 16:32 +0800
Re: TCP/IP options Paul Edwards <mutazilah@gmail.com> - 2024-03-26 19:34 +0800
Re: TCP/IP options Paul Edwards <mutazilah@gmail.com> - 2024-03-26 19:53 +0800
Re: TCP/IP options Paul Edwards <mutazilah@gmail.com> - 2024-03-27 07:36 +0800
csiph-web