AltME: R3 Protocols


Probably why my version times out on a 5Mb file after a minute

Graham, I made some corrections to the tls scheme so the problems(eg. write from connect and the port/data compatibility) you reported should be fixed. Please get it from here and give it a try.
Will try it today. Thanks.

Awake-event: lookup
** Script error: rc4 is missing its crypt-key argument
** Where: unless switch encrypt-data encrypted-handshake-msg parse do-commands
f switch -apply- wake-up loop -apply- wait read
** Near: unless ctx/encrypt-stream [
    ctx/encrypt-stream: rc4/key ...
Ah, sorry. It seems the code is 'too new'..we need to make new release of R3 Saphirion fork so you are able to run it.
First 5 minutes of testing shows that in  the new release, the tls port is now more like the tcp port

Could use R2 probably, but - can R3 read ftp? I will soon need small script for my LED screen client, who requests placing commercials himself. So my idea is to allow them to place it to FTP server, then my script takes it, downloads it, and rewrites the file locally ...
There's no ftp protocol built into R3, and I haven't heard of anyone making one. Maybe Kaj's curl wrapper can do ftp.
When I look at dev-net.c source it seems like UDP is only one switch. Would it be the UDP actor the same as for TCP or may it be less complicated?
The cURL binding can do FTP, of course
We've been uploading our websites with it for several years
I wrote a ftp scheme three years ago ... and was able to download ISO images with it.
Pekr, you forget so quickly!
As do I :)
to sys/make-scheme
and it should work. I did test it a week ago to confirm this.
Graham - I do remember VERY well in fact :-) But I was not sure it is recent and working with latest R3 releases. I would really like R3 to accept some protocols as standard ...
the work I was doing recently was turning these old efforts into synchronous forms as in R2
I have this unanswered question on how to deal with network timeouts
that I need answered.  I'd like some automatic way for tcp to update the waitlist somehow so that if network activity is occuring, the port should not timeout.
any takers?
In R2 you just increase the system timeout value prior to starting your network call

Last message posted 215 weeks ago.