Ahh, I see. I was thinking client. Now I wonder why you would "need" to
be able to tell the server to import locally from a remote client. I
could see uses for being able to import directly on the server for
maintenance or setup, but it seems it might be safer to not allow a
client to tell the server to import.
Is there a particular scenario that this would be used for that
couldn't be handled by scripting the server on the server computer, or
by importing in from a client?
Kevin
On Mar 31, 2004, at 10:49 AM, Ruslan Zasukhin wrote:
> On 3/31/04 6:48 PM, "Kevin Windham" <kevo /at/ gatorgraphics D.O.T com> wrote:
>
>> How would you import from another computer? Does cursor.import support
>> using network protocols?
>
> Hi Kevin,
>
> Import happens on SERVER computer.
>
> This is why I say that client must send to server path valid for SERVER
> computer.
>
> Please note all, that this is till subject for changes,
> Because I afraid such feature can be used for hacking -- bad guy can
> start a
> lots of exports and eat all HDD space of SERVER computer.
>
> We will need think more deep about this.
>
>> Kevin
>>
>> On Mar 31, 2004, at 7:56 AM, Ruslan Zasukhin wrote:
>>>
>>> Added
>>> cursor.Import( Path as string, ... )
>>> cursor.Export( Path as string, ... )
>>>
>>> Because I have not found way to use FolderItem in RB to specify path
>>> of
>>> other computer.
_______________________________________________
Valentina mailing list
Valentina@lists.macserve.net
http://lists.macserve.net/mailman/listinfo/valentina
©2004 Kevin Windham |
