Re: problems with send and macosx .3.3

2004-05-21 Thread [EMAIL PROTECTED]
sorry, my delimiters are numToChar(1) and numToChar(2).. logins/passwords are iso-8859-1 (aka us-ascii) chars only.. -Original Message- Could the passwords that don't work include any of the delimiters in tTransactionData? ___

Re: problems with send and macosx .3.3

2004-05-20 Thread Dar Scott
On Wednesday, May 19, 2004, at 08:09 PM, [EMAIL PROTECTED] wrote: do (send QUOTE tTransactionDataA[transaction] tTransactionData QUOTE to stack QUOTE sRegisteredTransactionsA[tTransactionDataA[transaction]] QUOTE in 0 milliseconds) Maybe this is equivalent: send

Re: problems with send and macosx .3.3

2004-05-20 Thread Dar Scott
On Wednesday, May 19, 2004, at 08:09 PM, [EMAIL PROTECTED] wrote: tTransactionDataA[] is an array containing all of the data tTransactionData is the same array, but as a flat string Could the passwords that don't work include any of the delimiters in tTransactionData? Dar Scott

Re: problems with send and macosx .3.3

2004-05-20 Thread Pierre Sahores
Hi, The way i would use, instead : - use the post/http methods - send a sequence of name1=value1name2=value2name3=value3etc... - catch the socket incoming message, on the server-side Rev's app as a PostIn global - set up a paramsswitcher handler able to parse the PostIn var and to pass requests

Re: problems with send and macosx .3.3

2004-05-19 Thread Pierre Sahores
Hello Shao, I'm not sure to understand the way you are using to send the login/password messages from each client-side app to the server-side app... POST, GET, under HTTP ? Could you, please, explain a little more how this process is handled ? I use POST/HTTP to manage such kind of stuffs under

Re: problems with send and macosx .3.3

2004-05-19 Thread Dar Scott
On Tuesday, May 18, 2004, at 09:31 PM, [EMAIL PROTECTED] wrote: now the really weird part to all of this is the fact that my password in the runrev app is base64 encoded and is the same as my macosx login password.. and!! if i include my password anywhere in the data being sent for the

Re: problems with send and macosx .3.3

2004-05-19 Thread Dar Scott
On Tuesday, May 18, 2004, at 09:31 PM, [EMAIL PROTECTED] wrote: all the information is being sent from the client to the server and is completely intact before the send command (the actually send command is being sent with the do command do to the complexity of it).. If it works, it works, but...

Re: problems with send and macosx .3.3

2004-05-19 Thread [EMAIL PROTECTED]
I'm not sure to understand the way you are using to send the actually, the client sends the login/password through a custom protocol to the server (the client and server communicate via tcp/ip).. the server socket receives the data and then uses the send command to send the data received to

Re: problems with send and macosx .3.3

2004-05-19 Thread [EMAIL PROTECTED]
Could you have left in some temporary script lines to do a quick password check? i originally thought that's what i may have done, but after printing all the scripts out and going through line-by-line (as well as a search in ms word), nothing showed up.. i'm tempted to change my system-level

Re: problems with send and macosx .3.3

2004-05-19 Thread [EMAIL PROTECTED]
Are you talking about the Transcript command, 'send'? yes If so, it need not be complex. The command parameter may be a variable. The object parameter may be a variable specifying the object (such as the long id). my line of code is: do (send QUOTE tTransactionDataA[transaction]

problems with send and macosx .3.3

2004-05-18 Thread [EMAIL PROTECTED]
i'm developing a program in runrev 2.1 on macosx .3.3 (aka panther) and have noticed something weird when using the send command.. i have a multi-user network-enabled intranet program, and during the testing of the login/password everything went smoothly until i decided to use someone else's