levigross's comments

levigross | 10 years ago | on: A Go “clone” of the great and famous Requests library

Whats wrong with "demand-creating" channels? The Go stdlib does it within their network library https://golang.org/src/net/singleflight.go#L67

levigross | 10 years ago | on: A Go “clone” of the great and famous Requests library

I know... But as you said (and I agreed) :) dependencies add complexity...

levigross | 10 years ago | on: A Go “clone” of the great and famous Requests library

I agree with this sentiment and therefore my Response method is also an `io.ReadCloser` (exposing the http.Response.Body io.ReadCloser that Go has to offer).

levigross | 10 years ago | on: A Go “clone” of the great and famous Requests library

I agree with you.

I wrote this library because I didn't want to rewrite those functions every time I started on a new project. I put it online because I figured that I would be useful to others as well.

levigross | 10 years ago | on: A Go “clone” of the great and famous Requests library

I am not trying to do things in the "Python way". I am trying to bring some of the same flexibility I get when using the Python requests library to Go.

levigross | 10 years ago | on: A Go “clone” of the great and famous Requests library

Jerf,

1. Thank you for the feedback

As you have already seen, I submitted my library to /r/golang and have gotten a lot of feedback – from which I modified the constructs (originally the functions returned channels).

I want to write something that is useful to as many people as possible (all while not alienating anyone) and therefore try not to force users (like I originally did) to use the "asynchronous APIs".

I didn't expect this to end up on HN and was going to start a discussion on golang-nuts on the pros and cons of this construct. Based on that, I was going to remove or keep the APIs.

levigross | 10 years ago | on: A Go “clone” of the great and famous Requests library

Originally the API was completely asynchronous (every "request" function returned a channel).

I got a lot of feedback that I shouldn't do that, so I moved the asynchronous requests to specific functions e.g GetAsync and made the standard API synchronous.

levigross | 10 years ago | on: A Go “clone” of the great and famous Requests library

yes

levigross | 10 years ago | on: A Go “clone” of the great and famous Requests library

I am not very good at naming things and figured to just slap a 'g' on requests => grequests.

I figured that I would write the code and decide on a name later...

levigross | 10 years ago | on: A Go “clone” of the great and famous Requests library

Jerf,

Thank you for the suggestion. I plan on adding some functionality to make asynchronous APIs friendlier to use (like a `Do` or `Apply` function etc...). But if you don't choose to use the asynchronous APIs everything still functions the same (in fact the asynchronous APIs use the synchronous functions and slap channels on them)

levigross | 10 years ago | on: A Go “clone” of the great and famous Requests library

I agree! The README is really sparse right now (I didn't expect so much exposure right). It is just a matter of time before the README has more information.

levigross | 10 years ago | on: A Go “clone” of the great and famous Requests library

Thanks – I wrote this library because I like using requests when writing in Python and wanted something similar when writing in Go.

levigross | 13 years ago | on: Web App Security Best Practices

This is true, however with creating applications with Django you are protected against most basic attacks. The ORM uses parameterized queries, all unsafe output is automatically escaped, Protection against CRLF injection within the framework and protection against HTTP response splitting.

The framework isn't fool proof (no one can protect developers from themselves). But I feel that Django does what it needs to do when it comes to protecting its users.

levigross | 14 years ago | on: SSH Key Audit on Github (required)

They also added a audit log so you will be able to track and address any future issues.. https://github.com/settings/security

levigross | 14 years ago | on: How to answer "What is your greatest weakness?"

I always answer "bullets" and get a blank stare in response.

levigross | 14 years ago | on: Diginotar confirms security breach

This is an Über Failure if I have ever seen one. They detected the breech on July 19th but didn't think to check to see if anything was amiss?!? I think that OS companies and browsers must come down hard on compromised certificate authorities. A ZERO tolerance policy should be enforced resulting in a permanent BAN if your private keys are compromised!

levigross | 14 years ago | on: Gmail.com being MITM'd by Iran using this certificate

This attack could of hit people in other countries as well. Small well places malicious BGP updates can reroute traffic into Iran.....

levigross | 14 years ago | on: Mark Cuban: What Business is Wall Street in?

I don't mean to praise wall street but Mark Cuban made his initial cash from stock options the same things the people on wall street trade. So he knows very well what businesses they are in.. They made him rich!

levigross | 14 years ago | on: Microsoft Responds To Google’s Response To Microsoft’s Response

+1 on the title

levigross | 14 years ago | on: Tom Pinckney: Why I gave up on Java and switched to Python

I agree that number 2 doesn't make any sense. I know that code quality is measured by defects in KLOC (1k lines of code) but this isn't a reason.

P.S Even though within the article the python the he explains what he means (with type bugs) such issues won't be by moving to python.