> Transporting media in a secure manner over the Web is inherently
> problematic, but as long as we're moving media around in a MetaCard
> stack it raises an interesting question ...
This is slightly tangential
but I have a different problem that is somewhat related.
When you use the post command to fetch a file/resource,
the response of the server that is put into a variable
and written to disk (in binary mode) by the client. But
the final result is a file with no identity that cannot
be dragged-and-dropped on the app that it is destined for,
even when the transfer takes place between two Macs.
I use an AppleScript droplet to give it back its true identity,
but I was wondering whether there was a MetaCard-native way of
specifying filetype and/or creator of a (fetched) file.
PS: The tangential link is that transporting media over the Web
in a 'secure' manner is problematic for me too, in the sense that
the file's identity is lost in transit.
Alain Farmer
mailto:[EMAIL PROTECTED]
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at
http://webmail.netscape.com/
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
