> But doesn't this mean that a remote (client) would intiate a
> process that results in writing to a server? Otherwise why
> call it a server?
I'd be surprised if every application on a server did nothing but listen for
& send client messages thru the wires. Suppose the original poster were
writing a server-side app that needed to keep a log file, make changes to an
.ini, or keep its own preferences? Any of these would require disk IO
(albeit not necessarily via FileIO Xtra).
> how would you propose to use director without a gui?
Don't use the stage. Example: I wrote an app a few months ago that reads
from & writes to a network ODBC data source, verifies files, sets up a
directory structure, does internal & external image manipulation, composites
& exports .jpg & .tif files, builds & prints hi-res graphics, etc, without
using the stage. It's called externally at the command line by a separate
process.
> And how would it be used as an EXE on a server.
I've written several others that run from the command line on servers. Ie.,
user uploads video clip to server, clip is received by server-side process
that calls a Director .exe that rips a still image from the clip & returns a
url to the new image.
> I hope I am not coming off as rude, because I am truly curious.
No rudeness heard here; it's not my intention either.
Regards,
Rob
/*********************************
* Rob Wingate, Software Human *
* http://www.vingage.com *
* mailto:[EMAIL PROTECTED] *
*********************************/
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
