From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Re: OAuth2 implementation in Elisp Date: Mon, 26 Sep 2011 21:55:40 +0200 Message-ID: <87vcsfhydf.fsf@thinkpad.tsdh.de> References: <87sjnojl7j.fsf@keller.adm.naquadah.org> <4E7BAFA4.8090800@dogan.se> <4E7BAFE2.2090102@dogan.se> <87k490jkaw.fsf@keller.adm.naquadah.org> <87d3eo984j.fsf@lifelogs.com> <87mxdsbx1n.fsf@keller.adm.naquadah.org> <87litc695c.fsf@lifelogs.com> <87vcsfmxzd.fsf@keller.adm.naquadah.org> <87y5xb4bgj.fsf@lifelogs.com> <87ehz32vm5.fsf@keller.adm.naquadah.org> <8762kf2uzg.fsf@keller.adm.naquadah.org> <87zkhr15pi.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1317066955 29964 80.91.229.12 (26 Sep 2011 19:55:55 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 26 Sep 2011 19:55:55 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 26 21:55:49 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1R8HHJ-0007Kt-7n for ged-emacs-devel@m.gmane.org; Mon, 26 Sep 2011 21:55:49 +0200 Original-Received: from localhost ([::1]:33547 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R8HHI-0000ud-PF for ged-emacs-devel@m.gmane.org; Mon, 26 Sep 2011 15:55:48 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:50598) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R8HHF-0000uF-MI for emacs-devel@gnu.org; Mon, 26 Sep 2011 15:55:46 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R8HHD-0005ON-HZ for emacs-devel@gnu.org; Mon, 26 Sep 2011 15:55:45 -0400 Original-Received: from out4.smtp.messagingengine.com ([66.111.4.28]:43377) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R8HHD-0005OB-FN for emacs-devel@gnu.org; Mon, 26 Sep 2011 15:55:43 -0400 Original-Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 93B2E2AB92 for ; Mon, 26 Sep 2011 15:55:42 -0400 (EDT) Original-Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute3.internal (MEProxy); Mon, 26 Sep 2011 15:55:42 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=from:to:subject:references:date :in-reply-to:message-id:mime-version:content-type; s=smtpout; bh=SYPKTpGzF2mewew8EQG8UPe8Hyo=; b=Pb3xUAXTqSSSixb8ZPHht4YKr1k5 u+zNJY/44YsUiTcs5zaKm4r34iLfoPaYRcmNTYiiGqZWBAHgY9B+xSYx8+3G3zRs xki9A6YZrpyTrNPGonj4Ea9DDSwF25+1WqcEmfVwrc1eqvusSF5qCnDbvogCDKMZ 62s4g2PPwSIIuTs= X-Sasl-enc: wxjbpnP5Fs2bZFJhUIy/FunoNKZaS0TxlKDIDoNZN4bY 1317066942 Original-Received: from thinkpad.tsdh.de (91-67-169-145-dynip.superkabel.de [91.67.169.145]) by mail.messagingengine.com (Postfix) with ESMTPSA id E8B5E680149 for ; Mon, 26 Sep 2011 15:55:41 -0400 (EDT) In-Reply-To: <87zkhr15pi.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 26 Sep 2011 14:09:13 -0500") User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.90 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 66.111.4.28 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:144349 Archived-At: Ted Zlatanov writes: >>> The format of the page is not standard, so there's no way you can >>> display it in Emacs. Really. > > j> I know nothing about this but out of curiousity: could it in principle > j> be done using the emacs xwidget webkit branch? There is some support to > j> access the DOM etc. there. > > SHR (see gnus/shr.el) could probably do it too, and it's in the trunk > already. But I'd rather pretend we're a web app and skip even this step > if possible, following the URL redirects instead. I think that's > possible based on my reading of the IETF OAuth2 draft. I don't know the OAuth spec, but you seem to imply that the pages showing the yes-no-buttons and the authentication code need to be HTML. But I understand Julien so that this is really arbitrary: some JavaScript that has to be interpreted, an image, a video (with 30 seconds beer ad before), or even some flash stuff. Bye, Tassilo