Rest of the text, obfuscated by long time AltME bug: "I don't know what version of R3 I am using, because there's no official version, I have something different installed on different machines, but I use it everyday and it works. With limitations, thanks to many R3 bugs."
To get around that bug, I just copy the entire message and paste it in the message field of AltME. ;-)
Thanks, I just haven't posted a link on AltME for some time, so I forgot about it's limitations ;)
Anyway, there's write and read support and it also properly handles writes longer than 32000 bytes.
You can patch R2 to handle longer writes as well, thanks to Max. I doubt this affects too much at this point though.
yes the simple R2 fix allows to POST any size.
Anyone else notice this strange behaviour (Atronix R3 on Windows):
The bottom is the way Rebol2 behaved, and the top is the way that Rebol3 seems to behave.
>> round/to to money! 3 $.01 == $3.00
>> round/to $3 $.01 == $3.00
Hi, I have 2 servers, one with SQL Server installed and another where users work. I need to have a rebol app on the first server which receives some commands and return one or more result sets of a query to its rebol caller app part on the other server. No need for async operation a sync one is sufficient. Have you some code example
I don't have example code, and don't use R3 in production at this point, but have you considered just using req/rep files on the FS? Just have your app look for %*.req files, run the query in them, and write out a %.rep file of the same name for the client to watch for. You can do it with net protocols, 0MQ, etc. but then you may need to be concerned about data size and such.
I'd rather prefeer direct server to serve communication, but if it is the only option I will use a file syste watcher.
Also, how do I read command line arguments in REBOL 3 ?