More Agraffee

[Ron Torrella]

On Sat, 8 Jul 1995 PianoGuru@aol.com wrote:

> The problem is that most Tech Bulletins include illustrations, which don't
> work too well across the 'Net.  While it is possible to send illustrations,
> it requires a certain amount of "tweeking" for the sender and receiver.  It
> also requires the graphics to be a separate file from the text, taking it
> somewhat out of context from the original printed bulletin.  Furthermore,
> graphics file require a large amount of memory, significantly increasing
> download time.
>
> Then, there is the issue of the appropriateness of "doing business" via a
> list server.  Or more to the point, is this doing business?

Here's how you get around the sticky issue of what may, to some, look like
propagandizing by manufacturers.  Simply make the stuff available--in
whatever form it may take, be it graphics or text or both--at an anonymous
server ftp site (I've still got plenty of space).  You're right, mailing
graphics is a little tricky when you're dealing with a gateway such as
BYU.  Graphics, as a rule,  prefer to travel non-stop from point to
point.  The brief layover at BYU has proven to be undesireable for
graphics files--at least in my experience.

At least while there's space, I'd be happy to store a few technicals on my
anon-servers (yes, I now have two).  It's easy enough to compress and
encode such files, so they shouldn't take up too much space.  Also, one
can get around the very large file problem by breaking it up into smaller
pieces.

Ron Torrella
School of Music         ** STANDARD DISCLAIMERS APPLY **
University of Illinois