Hi Jim,
Usually, I use open/read/close file, because it gives me more control
over the size of the chunks to be read. This allows be to create a
very smooth user experience.
I never checked it, but I presume that libUrl uses the same read/write/
close file commands to deal with local files, while it uses socket
communication for non-local files.
If I am right, issueing the read command yourself is a tiny fraction
of an i'th of a millisecond faster than using the put url command.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Dutch forum: http://runrev.info/rrforum/
Benefit from our inexpensive hosting services. See http://economy-x-talk.com/server.html
for more info.
On 20 sep 2008, at 06:32, Jim Sims wrote:
I've switched my rev cgi from my local Leopard webserver test area
to jaguarpc
and it seems that I must change some code.
I have a rev stack used as cgi and where put url worked on my Leopard
webserver it doesn't on jaguarpc. So, I changed to open file - read
from - close file.
My question is, does the "open - read - close" cycle of events
chew up more time than the put url? Is open-read-close the best way
or is there some
other means of putting a file into a variable (I already use custom
properties in the stack
for storing files and using them but am experimenting with the cgi
stack
grabbing files for use).
sims
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
