Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

REST API #26

Closed
snunez1 opened this issue Jun 18, 2014 · 2 comments
Closed

REST API #26

snunez1 opened this issue Jun 18, 2014 · 2 comments

Comments

@snunez1
Copy link

snunez1 commented Jun 18, 2014

Does anyone have any suggestions for interacting with a REST-ful API? There doesn't seem much in the way of support for this, and I don't have the time to build one from a socket interface.

Any modules that can be added to scsh for this?

@roderyc
Copy link
Member

roderyc commented Jun 24, 2014

It would probably make more sense to use other newer unix tools purpose built for that task, like httpie and jq. Just like with any other unix tool, you'd use scsh when you needed to create complex pipelines and coerce scheme data to / from their input / output to do more complex work than what you would with simple pipelines in bash.

It makes more sense to me to use scsh to its strengths (leveraging unix and dealing with its shittier parts) rather than adding scheme specific apis to it. Especially with limited time and resources.

@snunez1
Copy link
Author

snunez1 commented Jun 24, 2014

Yes, I kind of came to the same conclusion myself and began using curl. I¹ll
check out httpie and jg though. Thanks

From: Roderic Morris notifications@github.com
Reply-To: scheme/scsh
<reply+i-36012358-f58c2d1cabe50f93b051ba0040a9a124df6f2f0a-7775472@reply.git
hub.com>
Date: Monday, June 23, 2014 at 18:40
To: scheme/scsh scsh@noreply.github.com
Cc: Steve Nunez snunez@hortonworks.com
Subject: Re: [scsh] REST API (#26)

It would probably make more sense to use other newer unix tools purpose
built for that task, like httpie https://github.com/jakubroztocil/httpie
and jq http://stedolan.github.io/jq/ . Just like with any other unix tool,
you'd use scsh when you needed to create complex pipelines and coerce scheme
data to / from their input / output to do more complex work than what you
would with simple pipelines in bash.

It makes more sense to me to use scsh to its strengths (leveraging unix and
dealing with its shittier parts) rather than adding scheme specific apis to
it. Especially with limited time and resources.


Reply to this email directly or view it on GitHub
#26 (comment) .

CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.

@roderyc roderyc closed this as completed Jan 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants