Hello [EMAIL PROTECTED] actually to bo....
On 26-Sep-99, [EMAIL PROTECTED] wrote:
j> RE: [REBOL Helpdesk] assigned #749
j> Date:
j> Thu, 9 Sep 1999 15:48:39 -0700
j> From:
j> [EMAIL PROTECTED]
j> To:
j> [EMAIL PROTECTED]
j> Jim,
j> REBOL can listen to or write to any TCP port, including 443. However, the
j> HTTPS protocol is not yet supported. It is slated to be included in
j> REBOL/command which is due for release in November.
j> If you have any further questions, please let me know!
j> --
OK, not that the question has been raised... I'm curious as to how
you are going to go about supporting SSL. I know on the Amiga
platform the direction of SSL support has been halfway roll-your-own
and halfway support the API of one of the shared approaches (currently
only Miami-SSL (for Miami only) and AmiSSL (recently released, but
supposed to be universal). I don't know about other platforms tho. (I
have both installed, and have yet to notice any conflicts twixt the
two...)
One of the advantages of supporting an existing API is you don't have
to go through the hassle of supporting US versions and International
versions of similar code. (One of the problems, tho is you have no
control over the bugs in the SSL handling...)
I'm just curious to your (REBOL's) current plans. Support a specific
API for each platform, or roll your own code?
Pax
--
Member: Team AMIGA --} WatchDog
Fingerprint: 2C 8A 03 3C D6 D3 32 7F (Chris Elliott)
66 0F 9B 9F 03 77 1D 85 PGP Key ID: A6A79259
<tsb>"He talks to *farts*, man!" --Magic Nose Goblin
