Good point about the credentials. Proxy sounds like the way to go. I'd
appreciate seeing the php code you have when you are ready to share it.
Thanks.
On Nov 3, 2014, at 6:37 AM, nitin arora wrote:
> I agree with Karen: due to the sensitive info and the Summon API terms of
> service it's i
I agree with Karen: due to the sensitive info and the Summon API terms of
service it's important to avoid exposing your credentials - same reason
nobody probably has or will offer a public proxy to the Summon API as
mentioned in the embedded email from Oct. 26.
On the other hand, you can create a
We're working on a Sierra API wrapper to make the API much easier to work with.
The project code can be found at https://github.com/cudevmaxwell/tyro
An example using ajax can be found here:
https://github.com/cudevmaxwell/tyro/blob/master/static/index.html
It's in alpha right now. Feel free t
I don't know what the Summon API uses to authenticate clients. It looks
from the Python code like a key and secret is involved. You should be care
about embedding these API credentials (key/secret) in a Javascript. This
makes them available for anyone copy and use.
Karen
On Sun, Nov 2, 2014 at 4:
Has anyone constructed Summon API queries in javascript? (assuming that they
can be constructed to use jsonp and avoid cross domain problems …???)
Subject:
Re: Q: Summon API Service?
From:
Doug Chestnut
Reply-To:
Code for Libraries
Date:
Wed, 27 Oct
Looks like a more recent version of the Ruby library can be found here:
https://github.com/summon/summon.rb
Jason
On Tue, Oct 26, 2010 at 6:46 PM, Godmar Back wrote:
> Hi,
>
> Unlike Link/360, Serials Solution's Summon API is extremely cumbersome to
> use - requiring, for instance, that request
list.
- Demian
> -Original Message-
> From: Code for Libraries [mailto:code4...@listserv.nd.edu] On Behalf Of
> Godmar Back
> Sent: Tuesday, October 26, 2010 6:46 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: [CODE4LIB] Q: Summon API Service?
>
> Hi,
>
> Unlike Link
Hi,
Unlike Link/360, Serials Solution's Summon API is extremely cumbersome to
use - requiring, for instance, that requests be digitally signed. (*)
Has anybody developed a proxy server for Summon that makes its API public
(e.g. receives requests, signs them, forwards them to Summon, and relays th
