Received: by 10.91.34.26 with SMTP id m26mr1808648agj.26.1298595264737;
        Thu, 24 Feb 2011 16:54:24 -0800 (PST)
X-BeenThere: plancast-api@googlegroups.com
Received: by 10.90.59.39 with SMTP id h39ls238023aga.6.p; Thu, 24 Feb 2011
 16:54:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.90.86.10 with SMTP id j10mr249534agb.5.1298595264285; Thu, 24
 Feb 2011 16:54:24 -0800 (PST)
Received: by k15g2000prk.googlegroups.com with HTTP; Thu, 24 Feb 2011 16:54:24
 -0800 (PST)
Date: Thu, 24 Feb 2011 16:54:24 -0800 (PST)
X-IP: 75.140.5.143
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-US)
 AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.102 Safari/534.13,gzip(gfe)
Message-ID: <2c953950-ae54-4ea1-872f-a15776b71d65@k15g2000prk.googlegroups.com>
Subject: SSL planned for authentication required calls?
From: noinput <noin...@gmail.com>
To: Plancast API <plancast-api@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1

Is there a reason that SSL is not available when sending passwords in
plaintext?  I'd love to build an app off the API but there are too