It is definitely illuminating, but doesn't answer my question...
Gabriele
- as to how async-modes work, it was never documented. the only documentation are my async:// and Romano's atcp:// - as to why it works that way, it was probably a kludge; only Carl knows the details - if you want to learn your best bet is to build something with it, it will then fail in a weird way, and you'll spend a few weeks trying to figure out why it failed (hopefully the existing code will give you hints and it won't be that bad...); iterate that a few times and you'll have a general idea - I don't think I had much influence on the native side of R3, my contribution was mostly the HTTP scheme, which was incomplete because I was waiting for Carl to answer some questions and implement a couple things on the native side
Chris
Thanks Gab!
DideC
Soon, I will have to code the server part of a Webservice in R2 (maybe r3). Is there any already library available to minimise the work?
DideC
I already use altjson.r and altwebform.r to access Webservice as client. I also have curl.r and rest-curl.r.
Maybe Chris has some advice to help me? ;-)
...please
Endo
If you will consume a webservice using R2 as a client, remember that R2 cannot make requests to most of modern servers because of the SSL issues. >> read https://openssl.org connecting to: openssl.org ** Command Error: SSL Error: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
So using cURL is a better option (or R3 or Red)
DideC
yes. but in my case, it will be the server!
Chris
QuarterMaster still works (R2), but I'm afraid other than a couple of examples, asking me is probably your best bet for documentation.