> Does anyone have an example of using #:tls-encode (net/smtp)?
No, in fact I'm seeing it fail today with an SMTP server that requires
TLS on port 587.
The reason seems to be that the server is expecting AUTH LOGIN whereas
net/smtp only does AUTH PLAIN.
I was able to get it to work (with this pa
please how can i edit this code in order to define a constant twopower
function,which will look similar to the following definition:
(define twoplus ’{fun {n} { n 2}})
Of course, twopower should not implement the function n 2, but 2n, for n a
non-negative integer.
for example if we use this
I just pushed an update. Thanks.
Jay
2011/3/5 Alok Thapa :
> Hi,
>
> I've been using the racket webserver to build websites and found this minor
> bug ( omission) in response/xexpr file where it's contract does not take the
> #:cookie parameter when it should. Here's the link to the documentation
Yes, I've heard that and will seemingly feel it as well in N years time.
> -Original Message-
> From: Matthias Felleisen [mailto:matth...@ccs.neu.edu]
> Sent: 07 March 2011 16:01
> To: Jukka Tuominen
> Cc: users@racket-lang.org
> Subject: Re: [racket] Liitin screencast tutorial
>
>
>
> O
On Mar 7, 2011, at 2:30 AM, Jukka Tuominen wrote:
> (sorry, I took the days from wheather forecasting :)
>
> Now, how likely is that _any_ data/program out there now will just
> work/exist after 50 years?
Sounds like you're discussing global warming but it fits to software too.
As the first
Sorry, absolutely nothing personal (cosi fan tutti)
- It works/exists today (Racket 5.1)
- It it very likely to work/exist tomorror, as well. (PLT 4.25)
- It will propably work/exist day after (PLT 4.0)
- On third day it's 50:50 (PLT 300)
- after fifth day you are better off reading from frog's
6 matches
Mail list logo
