Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Create A Drop - Default View not optional

Received: by 10.91.121.9 with SMTP id y9mr823976agm.33.1271521022788;
        Sat, 17 Apr 2010 09:17:02 -0700 (PDT)
X-BeenThere: dropio-api@googlegroups.com
Received: by 10.90.216.14 with SMTP id o14ls6702846agg.5.p; Sat, 17 Apr 2010 
	09:17:02 -0700 (PDT)
Received: by 10.90.10.20 with SMTP id 20mr1244042agj.0.1271521022173;
        Sat, 17 Apr 2010 09:17:02 -0700 (PDT)
Received: by 10.90.10.20 with SMTP id 20mr1244041agj.0.1271521022108;
        Sat, 17 Apr 2010 09:17:02 -0700 (PDT)
Return-Path: <ja...@dropio.com>
Received: from mail-gw0-f45.google.com (mail-gw0-f45.google.com [74.125.83.45])
        by gmr-mx.google.com with ESMTP id 11si394806gxk.5.2010.04.17.09.17.02;
        Sat, 17 Apr 2010 09:17:02 -0700 (PDT)
Received-SPF: neutral (google.com: 74.125.83.45 is neither permitted nor denied by best guess record for domain of ja...@dropio.com) client-ip=74.125.83.45;
Received: by gwj21 with SMTP id 21so1607743gwj.32
        for <dropio-api@googlegroups.com>; Sat, 17 Apr 2010 09:17:01 -0700 (PDT)
Received: by 10.101.202.7 with SMTP id e7mr7744050anq.33.1271521019193;
        Sat, 17 Apr 2010 09:16:59 -0700 (PDT)
Return-Path: <ja...@dropio.com>
Received: from bda358.bisx.prod.on.blackberry (bda-67-223-67-209.bise.na.blackberry.com [67.223.67.209])
        by mx.google.com with ESMTPS id 6sm1027893yxg.66.2010.04.17.09.16.57
        (version=SSLv3 cipher=RC4-MD5);
        Sat, 17 Apr 2010 09:16:57 -0700 (PDT)
X-rim-org-msg-ref-id: 1961942745
Message-ID: <1961942745-1271521015-cardhu_decombobulator_blackberry.rim.net-65056621-@bda830.bisx.prod.on.blackberry>
Reply-To: dropio-api@googlegroups.com
X-Priority: Normal
References: <efc1e13c-7f2f-4f8f-8e26-e8272c6d9bdb@g11g2000yqe.googlegroups.com><d0bb4ec3-2fe4-410d-ba42-bc4da27e9e0f@x3g2000yqd.googlegroups.com>
In-Reply-To: <d0bb4ec3-2fe4-410d-ba42-bc4da27e9e0f@x3g2000yqd.googlegroups.com>
Sensitivity: Normal
Importance: Normal
Subject: Re: [Drop.io API] Re: Create A Drop - Default View not optional
To: dropio-api@googlegroups.com
From: ja...@dropio.com
Date: Sat, 17 Apr 2010 16:17:11 +0000
MIME-Version: 1.0
X-Original-Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 
	74.125.83.45 is neither permitted nor denied by best guess record for domain 
	of ja...@dropio.com) smtp.mail=ja...@dropio.com
X-Original-Sender: ja...@dropio.com
Precedence: list
Mailing-list: list dropio-api@googlegroups.com; contact dropio-api+owners@googlegroups.com
List-ID: <dropio-api.googlegroups.com>
List-Post: <http://groups.google.com/group/dropio-api/post?hl=en_US>, 
	<mailto:dropio-api@googlegroups.com>
List-Help: <http://groups.google.com/support/?hl=en_US>, <mailto:dropio-api+help@googlegroups.com>
List-Archive: <http://groups.google.com/group/dropio-api?hl=en_US>
Sender: dropio-api@googlegroups.com
List-Subscribe: <http://groups.google.com/group/dropio-api/subscribe?hl=en_US>, 
	<mailto:dropio-api+subscribe@googlegroups.com>
List-Unsubscribe: <http://groups.google.com/group/dropio-api/subscribe?hl=en_US>, 
	<mailto:dropio-api+unsubscribe@googlegroups.com>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=ISO-8859-1

That's a good idea Karl. We were looking at the tools twitter uses for thei=
r API and they have a bugtracker in google code. I'll talk about it with Er=
ic, he's busy organizing barcamp this weekend but I think he has some thoug=
hts about how we should manage api tracking.



-----Original Message-----
From: Karl Freeman <karlfree...@gmail.com>
Date: Sat, 17 Apr 2010 06:55:34=20
To: Drop.io API<dropio-api@googlegroups.com>
Subject: [Drop.io API] Re: Create A Drop - Default View not optional

Also I wondered if perhaps another idea ( im full of them today ;) )
would be some sort of ticketing system? Like I feel a little guilty
doing a whole post to all the developers about something minor about
the api?

Keep up the hard work!
Karl.

On Apr 17, 2:54=A0pm, Karl Freeman <karlfree...@gmail.com> wrote:
> Sorry for a whole post about this but its just to let you know that
> when creating a drop using the 2.0 api and specifying a default_view I
> get 500 error's when its empty. Its easy to work around by setting a
> default my side but unless you specify eg "media" the api query fails.
> Perhaps you could set on your side a default when the default_view is
> empty or not a correct string?
>
> Cheers
> Karl.
>
> --
> You received this message because you are subscribed to the Google Groups=
 "Drop.io API" group.
> To post to this group, send email to dropio-api@googlegroups.com.
> To unsubscribe from this group, send email to dropio-api+unsubscribe@goog=
legroups.com.
> For more options, visit this group athttp://groups.google.com/group/dropi=
o-api?hl=3Den.

--=20
You received this message because you are subscribed to the Google Groups "=
Drop.io API" group.
To post to this group, send email to dropio-api@googlegroups.com.
To unsubscribe from this group, send email to dropio-api+unsubscribe@google=
groups.com.
For more options, visit this group at http://groups.google.com/group/dropio=
-api?hl=3Den.

--=20
You received this message because you are subscribed to the Google Groups "=
Drop.io API" group.
To post to this group, send email to dropio-api@googlegroups.com.
To unsubscribe from this group, send email to dropio-api+unsubscribe@google=
groups.com.
For more options, visit this group at http://groups.google.com/group/dropio=
-api?hl=3Den.