At 10:21 am -0800 12/12/02, Richard Gaskin wrote:
We can download stacks easily using the load command, followed by a go url
command once the file is cached.
However, if we want to transfer gzipped stacks we need some way to run the
url cache through the decompress function.
How can we accss
Dave Cragg wrote:
At 10:21 am -0800 12/12/02, Richard Gaskin wrote:
We can download stacks easily using the load command, followed by a go url
command once the file is cached.
However, if we want to transfer gzipped stacks we need some way to run the
url cache through the decompress
Dave Cragg wrote:
How can we accss the cache to alter it before using the go url command?
go stack decompress(url http://whatever.com/whatever.gz;)
How can that be used with the load command?
--
Richard Gaskin
Fourth World Media Corporation
Developer of WebMerge 2.1: Publish any
At 10:53 am -0800 12/12/02, Richard Gaskin wrote:
Dave Cragg wrote:
How can we accss the cache to alter it before using the go url command?
go stack decompress(url http://whatever.com/whatever.gz;)
How can that be used with the load command?
First:
load url
Dave Cragg wrote:
At 10:53 am -0800 12/12/02, Richard Gaskin wrote:
Dave Cragg wrote:
How can we accss the cache to alter it before using the go url command?
go stack decompress(url http://whatever.com/whatever.gz;)
How can that be used with the load command?
First:
load url
I don't think so. Here I get a not a stack error, which seems logical
once I thought it through.
Hi Richard
It may be a problem on the compression side. I use a compressed stack as a
custom file format for one of my apps and I use:
-- saving
save stack tName as pSave
put compress(url
At 3:47 pm -0800 12/12/02, Richard Gaskin wrote:
First:
load url http://whatever.com/whatever.gz; ##now in cache
then later:
go stack decompress(url http://whatever.com/whatever.gz;) ##will
take it from the cache
I don't think so. Here I get a not a stack error, which seems logical
Monte Goulding wrote:
It may be a problem on the compression side. I use a compressed stack as a
custom file format for one of my apps and I use:
-- saving
save stack tName as pSave
put compress(url (binfile:pSave)) into url (binfile:pSave)
-- opening
put decompress(url (binfile:tOpen))
I appreciate your chiming in here, Monte. I'll double-check my code, but
the implications of your presumably functioning code example
above are quite
a change to my understanding of things: I can use raw data (from a valid
stack file, of course) instead of a stack descriptor with the go
On 12/12/02 7:22 PM, Richard Gaskin wrote:
I appreciate your chiming in here, Monte. I'll double-check my code, but
the implications of your presumably functioning code example above are quite
a change to my understanding of things: I can use raw data (from a valid
stack file, of course)
Kind of cool, if it works.
Very cool if you write an app that needs to transfer data from one user's
version to another via email and want to save bandwidth. I didn't just come
up with the script off the top of my head I cut and pasted from the file
management library of my app. It works ;-)
Dave Cragg wrote:
I use this technique a lot so don't give up. Monte's point about
using compress on the binfile when making the compressed file may
be significant.
These are coming over the 'Net, and it seems the go url command faithfully
transfers binary files as such -- thanks to you and
On 12/12/02 7:43 PM, Monte Goulding wrote:
It works ;-)
I never really doubted you for a moment. ;)
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www.hyperactivesw.com
___
metacard mailing list
Actually I think you should doubt me most of the time ;-)
I've been accused of writing speculative drivel on the rev list today ;-P
On 12/12/02 7:43 PM, Monte Goulding wrote:
It works ;-)
I never really doubted you for a moment. ;)
--
Jacqueline Landman Gay | [EMAIL
14 matches
Mail list logo