Add simplest service/urlfetch implementation.

Add simplest service/urlfetch implementation.

R=iannucci@chromium.org
BUG=

Committed: https://github.com/luci/gae/commit/8dd23560160d7ee72beb1dff137efeff6757985c

[Vadim Sh., 2015-09-18 01:14:14]

This feels dumb :-/ But importing "google.golang.org/appengine" in apps that use
luci/gae feels even worse.

[Vadim Sh., 2015-09-18 01:15:02]

https://codereview.chromium.org/1354083002/diff/1/service/urlfetch/context.go
File service/urlfetch/context.go (right):

https://codereview.chromium.org/1354083002/diff/1/service/urlfetch/context.go...
service/urlfetch/context.go:30: return http.DefaultTransport
no memory implementation for now because this covers it :-/

[iannucci, 2015-09-18 01:19:38]

lgtm

https://codereview.chromium.org/1354083002/diff/1/service/urlfetch/context.go
File service/urlfetch/context.go (right):

https://codereview.chromium.org/1354083002/diff/1/service/urlfetch/context.go...
service/urlfetch/context.go:30: return http.DefaultTransport
On 2015/09/18 01:15:02, Vadim Sh. wrote:
> no memory implementation for now because this covers it :-/

but this means that it'll be making actual http access in tests? Or I
misunderstand?

[Vadim Sh., 2015-09-18 01:22:35]

https://codereview.chromium.org/1354083002/diff/1/service/urlfetch/context.go
File service/urlfetch/context.go (right):

https://codereview.chromium.org/1354083002/diff/1/service/urlfetch/context.go...
service/urlfetch/context.go:30: return http.DefaultTransport
On 2015/09/18 01:19:38, iannucci wrote:
> On 2015/09/18 01:15:02, Vadim Sh. wrote:
> > no memory implementation for now because this covers it :-/
> 
> but this means that it'll be making actual http access in tests? Or I
> misunderstand?

Well... One way of testing http stuff is actualy via loopback interface: 
http://golang.org/pkg/net/http/httptest/ 

What I meant by "coverts it": it won't panic with used. Presumably unit tests
will use urlfetch.Set(mockedTransport).

Should it panic by default?

[iannucci, 2015-09-18 01:23:31]

On 2015/09/18 01:22:35, Vadim Sh. wrote:
> https://codereview.chromium.org/1354083002/diff/1/service/urlfetch/context.go
> File service/urlfetch/context.go (right):
> 
>
https://codereview.chromium.org/1354083002/diff/1/service/urlfetch/context.go...
> service/urlfetch/context.go:30: return http.DefaultTransport
> On 2015/09/18 01:19:38, iannucci wrote:
> > On 2015/09/18 01:15:02, Vadim Sh. wrote:
> > > no memory implementation for now because this covers it :-/
> > 
> > but this means that it'll be making actual http access in tests? Or I
> > misunderstand?
> 
> Well... One way of testing http stuff is actualy via loopback interface: 
> http://golang.org/pkg/net/http/httptest/ 
> 
> What I meant by "coverts it": it won't panic with used. Presumably unit tests
> will use urlfetch.Set(mockedTransport).
> 
> Should it panic by default?

I would rather have it panic if there's no explicitly set implementation... but
maybe that's just me :)

[Vadim Sh., 2015-09-18 01:28:19]

ok, panics now

[Vadim Sh., 2015-09-18 01:28:33]

The CQ bit was checked by vadimsh@chromium.org

[Vadim Sh., 2015-09-18 01:28:34]

The patchset sent to the CQ was uploaded after l-g-t-m from
iannucci@chromium.org
Link to the patchset: https://codereview.chromium.org/1354083002/#ps20001
(title: "panic")

[commit-bot: I haz the power, 2015-09-18 01:28:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1354083002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1354083002/20001

[commit-bot: I haz the power, 2015-09-18 01:31:49]

Committed patchset #2 (id:20001) as
https://github.com/luci/gae/commit/8dd23560160d7ee72beb1dff137efeff6757985c