Date: Fri, 13 Jul 2012 08:51:46 -0700 (PDT) From: "Nicole (Craftybase)" <nicolejpas...@gmail.com> To: etsy-api-v2@googlegroups.com Message-Id: <1ecf81e3-a43c-43a3-b4c8-48cd6b3a1e32@googlegroups.com> In-Reply-To: <CACbj_yycfd+OgzYVLNM3_aG+kMQfVK7k3UyGGjrsz13LXH66aw@mail.gmail.com> References: <CAEy_azpJHxZJ-6dkEU5tDCuEpp=hkC76a8bqtPUH3ZeGSAcyjg@mail.gmail.com> <CAEy_azoWM7svDSNLQ2f3La5=xPFAbL4kuMiCPk+1NDe6shWr9A@mail.gmail.com> <28d26093-e445-4af7-ada2-f561fa3c2d3e@googlegroups.com> <CAEy_azp8NeaSvChS=PkmmT5EvOe0ogMr4rOiK8q-DXcgBzOJgw@mail.gmail.com> <CACbj_yycfd+OgzYVLNM3_aG+kMQfVK7k3UyGGjrsz13LXH66aw@mail.gmail.com> Subject: Re: [ANNOUNCE] Upcoming change to BillCharge findAllUserCharges API call MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_154_16950807.1342194706362" ------=_Part_154_16950807.1342194706362 Content-Type: multipart/alternative; boundary="----=_Part_155_15092266.1342194706362" ------=_Part_155_15092266.1342194706362 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I really need to know what Etsy now recommends as an approach now that the large offset is deprecated - changing my code to cycle right back to the user's join date is going to substantially add to the API calls I make as part of a user's initial import. As I only really now have this weekend to make these changes, can I please get a reply for this today if possible? Thanks, Nicole On Friday, July 6, 2012 5:11:31 PM UTC+1, Nicole (Craftybase) wrote: > > Thanks for the reply - it's the narrower query window, not the min / max > parameters that is going to cause the most amount of rework for me - I > essentially need some way of retrieving all of a user's historical bill > payments when a new user starts with our app so that they initially have > their full bill charge history ready for analysis. If they don't have this > when they signup, then they are not going to see the full benefit of my app > :( > > If this window is going to be set, I'll have to change my code to > repeatedly cycle back in 31 day increments until I hit the initial join > date for the user (which is obviously going to cause more API calls in > total than the current solution)....unless there is a different way that is > recommended by Etsy? > > > On Thu, Jul 5, 2012 at 10:34 AM, Paul Wright <pwri...@etsy.com> wrote: > >> Hi Nicole, >> >> Firstly, thanks for getting in touch. I appreciate that not every app >> has an army of developers working full time on it. >> >> We're trying to limit the scope of impact with this issue to the paging >> of results - switching from large offsets to narrower timestamp windows as >> the desired access pattern for a user's bill charges. >> >> It's very possible this isn't the only use case of this API call and if >> this is the case I'd love to hear how developers are using it, that would >> help us. >> >> Cheers, >> >> Paul. >> >> >> On Mon, Jul 2, 2012 at 10:25 PM, nic <nicolejpas...@gmail.com> wrote: >> >>> Are these dates set in stone? These changes are going to require a >>> fairly significant rewrite of my codebase and I'm not 100% positive I will >>> be able to get these changes into production in the space of a mere 3 weeks >>> from now :( >>> >>> Please keep in mind that for many of us the weekends are the only time >>> we have to work on our apps, so from now gives us approximately 6 "working >>> days" to code, test and release - providing we don't actually have a spare >>> day off before now and the deadline - sigh :( >>> >>> I'd really appreciate at least a month at the bare minimum for notice on >>> these sort of big changes, especially if we are going to get hit with 400 >>> error responses if we fail to hit this date (which is obviously going to >>> affect our relationships with our users) - this approach seems quite harsh >>> to me to be honest? >>> >>> >>> Nicole >>> Craftybase >>> >>> On Monday, July 2, 2012 2:46:43 PM UTC+1, Paul Wright wrote: >>>> >>>> Apologies, those dates are July, rather than May. The actual time line >>>> is: >>>> >>>> * 07/02/12, today: notify the API mailing list and add a note to this >>>> effect to the developer's documentation. >>>> * 07/16/12, two weeks from now: monitor API requests and notify any >>>> developers relying on the old behavior. >>>> * 07/25/12, three weeks from now: switch over to the new behavior, any >>>> requests that do not include min_created and max_created will be returned a >>>> HTTP 400 error response. >>>> >>>> Cheers, >>>> >>>> Paul. >>>> >>>> On Mon, Jul 2, 2012 at 1:42 PM, Paul Wright <pwri...@etsy.com> wrote: >>>> >>>>> Hi everyone, >>>>> >>>>> To improve the response speed for API calls to BillCharge >>>>> findAllUserCharges (/users/:user_id/charges) we are planning to alter the >>>>> behaviour such that the min_created and max_created parameters become >>>>> mandatory and can be no more than 31 days apart. If only one of these >>>>> _created parameters is submitted in a request then the other will default >>>>> to +/-31 days as appropriate. >>>>> >>>>> http://www.etsy.com/**developers/documentation/** >>>>> reference/billcharge#method_**findallusercharges<http://www.etsy.com/developers/documentation/reference/billcharge#method_findallusercharges> >>>>> >>>>> As this is a behaviour change to this API call we intend to roll it >>>>> out over the following timeline: >>>>> >>>>> * 05/02/12, today: notify the API mailing list and add a note to this >>>>> effect to the developer's documentation. >>>>> * 05/16/12, two weeks from now: monitor API requests and notify any >>>>> developers relying on the old behavior. >>>>> * 05/25/12, three weeks from now: switch over to the new behavior, any >>>>> requests that do not include min_created and max_created will be returned a >>>>> HTTP 400 error response. >>>>> >>>>> We realise that this might result in some additional work but hope you >>>>> can appreciate that the current unrestricted approach slows down our >>>>> response and, indirectly, your applications. >>>>> >>>>> Cheers, >>>>> >>>>> Paul. >>>>> >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Etsy API V2" group. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msg/etsy-api-v2/-/9-ik8BHFR98J. >>> To post to this group, send email to etsy-api-v2@googlegroups.com. >>> To unsubscribe from this group, send email to >>> etsy-api-v2+unsubscribe@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/etsy-api-v2?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Etsy API V2" group. >> To post to this group, send email to etsy-api-v2@googlegroups.com. >> To unsubscribe from this group, send email to >> etsy-api-v2+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/etsy-api-v2?hl=en. >> > > ------=_Part_155_15092266.1342194706362 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <div>I really need to know what Etsy now recommends as an approach now that= the large offset is deprecated - changing my code to cycle right back to t= he user's join date is going to substantially add to the API calls I make a= s part of a user's initial import. </div><div><br></div><div>As I= only really now have this weekend to make these changes, can I please get = a reply for this today if possible?</div><div><br></div><div>Thanks,</div><= div><br></div><div>Nicole</div><div><div><br></div><div><br>On Friday, July= 6, 2012 5:11:31 PM UTC+1, Nicole (Craftybase) wrote:<blockquote class=3D"g= mail_quote" style=3D"margin: 0;margin-left: 0.8ex;border-left: 1px #ccc sol= id;padding-left: 1ex;">Thanks for the reply - it's the narrower query windo= w, not the min / max parameters that is going to cause the most amount of r= ework for me - I essentially need some way of retrieving all of a user's hi= storical bill payments when a new user starts with our app so that they ini= tially have their full bill charge history ready for analysis. If they don'= t have this when they signup, then they are not going to see the full benef= it of my app :(<div> <br></div><div>If this window is going to be set, I'll have to change my co= de to repeatedly cycle back in 31 day increments until I hit the initial jo= in date for the user (which is obviously going to cause more API calls in t= otal than the current solution)....unless there is a different way that is = recommended by Etsy?<div> <br><br><div class=3D"gmail_quote">On Thu, Jul 5, 2012 at 10:34 AM, Paul Wr= ight <span dir=3D"ltr"><<a href=3D"mailto:pwri...@etsy.com" target=3D"_b= lank">pwri...@etsy.com</a>></span> wrote:<br><blockquote class=3D"gmail_= quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1= ex"> Hi Nicole,<div><br></div><div>Firstly, thanks for getting in touch. I= appreciate that not every app has an army of developers working full time = on it. </div><div><br></div><div>We're trying to limit the scope of i= mpact with this issue to the paging of results - switching from large offse= ts to narrower timestamp windows as the desired access pattern for a user's= bill charges.</div> <div><br></div><div>It's very possible this isn't the only use case of this= API call and if this is the case I'd love to hear how developers are using= it, that would help us.</div><div><br></div><div>Cheers,</div> <div><br></div><div>Paul.<div><div><br><br><div class=3D"gmail_quote">On Mo= n, Jul 2, 2012 at 10:25 PM, nic <span dir=3D"ltr"><<a href=3D"mailto:nic= olejpas...@gmail.com" target=3D"_blank">nicolejpas...@gmail.com</a>></sp= an> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex">Are these dates set in stone? These changes = are going to require a fairly significant rewrite of my codebase and I'm no= t 100% positive I will be able to get these changes into production in the = space of a mere 3 weeks from now :( <div> <br></div><div>Please keep in mind that for many of us the weekends are the= only time we have to work on our apps, so from now gives us approximately = 6 "working days" to code, test and release - providing we don't actually ha= ve a spare day off before now and the deadline - sigh :(</div> <div><br></div><div>I'd really appreciate at least a month at the bare mini= mum for notice on these sort of big changes, especially if we are going to = get hit with 400 error responses if we fail to hit this date (which is obvi= ously going to affect our relationships with our users) - this approach see= ms quite harsh to me to be honest?</div> <div><br></div><div><br></div><div><div>Nicole</div><div>Craftybase</div><d= iv><div><div><br>On Monday, July 2, 2012 2:46:43 PM UTC+1, Paul Wright wrot= e:<blockquote class=3D"gmail_quote" style=3D"margin:0;margin-left:0.8ex;bor= der-left:1px #ccc solid;padding-left:1ex"> Apologies, those dates are July, rather than May. The actual time line is:<= div><br></div><div><div><span style=3D"white-space:pre-wrap">=09</span>* 07= /02/12, today: notify the API mailing list and add a note to this effect to= the developer's documentation.</div> <div><span style=3D"white-space:pre-wrap">=09</span>* 07/16/12, two weeks f= rom now: monitor API requests and notify any developers relying on the old = behavior.</div><div><span style=3D"white-space:pre-wrap">=09</span>* 07/25/= 12, three weeks from now: switch over to the new behavior, any requests tha= t do not include min_created and max_created will be returned a HTTP 400 er= ror response.</div> <div><br></div><div>Cheers,</div><div><br></div><div>Paul.</div><div><br></= div><div class=3D"gmail_quote">On Mon, Jul 2, 2012 at 1:42 PM, Paul Wright = <span dir=3D"ltr"><<a href=3D"mailto:pwri...@etsy.com" target=3D"_blank"= >pwri...@etsy.com</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><div>Hi everyone,</div><div><br></div><div>T= o improve the response speed for API calls to BillCharge findAllUserCharges= (/users/:user_id/charges) we are planning to alter the behaviour such that= the min_created and max_created parameters become mandatory and can be no = more than 31 days apart. If only one of these _created parameters is submit= ted in a request then the other will default to +/-31 days as appropriate.<= /div> <div><br></div><div><a href=3D"http://www.etsy.com/developers/documentation= /reference/billcharge#method_findallusercharges" target=3D"_blank">http://w= ww.etsy.com/<u></u>developers<wbr>/documentation/<u></u>reference/<wbr>bill= charge#method_<u></u>findalluserc<wbr>harges</a></div> <div><br></div><div>As this is a behaviour change to this API call we inten= d to roll it out over the following timeline:</div><div><br></div><div><spa= n style=3D"white-space:pre-wrap">=09</span>* 05/02/12, today: notify the AP= I mailing list and add a note to this effect to the developer's documentati= on.</div> <div><span style=3D"white-space:pre-wrap">=09</span>* 05/16/12, two weeks f= rom now: monitor API requests and notify any developers relying on the old = behavior.</div><div><span style=3D"white-space:pre-wrap">=09</span>* 05/25/= 12, three weeks from now: switch over to the new behavior, any requests tha= t do not include min_created and max_created will be returned a HTTP 400 er= ror response.</div> <div><br></div><div>We realise that this might result in some additional wo= rk but hope you can appreciate that the current unrestricted approach slows= down our response and, indirectly, your applications.</div><div><br></div> <div>Cheers,</div><div><br></div><div>Paul.</div> </blockquote></div><br></div> </blockquote></div></div></div></div><span><font color=3D"#888888"> <p></p> -- <br> You received this message because you are subscribed to the Google Groups "= Etsy API V2" group.<br> To view this discussion on the web visit <a href=3D"https://groups.google.c= om/d/msg/etsy-api-v2/-/9-ik8BHFR98J" target=3D"_blank">https://groups.googl= e.com/d/<wbr>msg/etsy-api-v2/-/9-ik8BHFR98J</a><wbr>.<br>=20 To post to this group, send email to <a href=3D"mailto:etsy-api-v2@googlegr= oups.com" target=3D"_blank">etsy-api-v2@googlegroups.com</a>.<br> To unsubscribe from this group, send email to <a href=3D"mailto:etsy-api-v2= %2Bunsubscribe@googlegroups.com" target=3D"_blank">etsy-api-v2+unsubscribe@= <wbr>googlegroups.com</a>.<br> For more options, visit this group at <a href=3D"http://groups.google.com/g= roup/etsy-api-v2?hl=3Den" target=3D"_blank">http://groups.google.com/<wbr>g= roup/etsy-api-v2?hl=3Den</a>.<br> </font></span></blockquote></div><br></div></div></div><div><div> <p></p> -- <br> You received this message because you are subscribed to the Google Groups "= Etsy API V2" group.<br> To post to this group, send email to <a href=3D"mailto:etsy-api-v2@googlegr= oups.com" target=3D"_blank">etsy-api-v2@googlegroups.com</a>.<br> To unsubscribe from this group, send email to <a href=3D"mailto:etsy-api-v2= %2Bunsubscribe@googlegroups.com" target=3D"_blank">etsy-api-v2+unsubscribe@= <wbr>googlegroups.com</a>.<br> For more options, visit this group at <a href=3D"http://groups.google.com/g= roup/etsy-api-v2?hl=3Den" target=3D"_blank">http://groups.google.com/<wbr>g= roup/etsy-api-v2?hl=3Den</a>.<br> </div></div></blockquote></div><br></div></div> </blockquote></div></div> ------=_Part_155_15092266.1342194706362-- ------=_Part_154_16950807.1342194706362--
Message from discussion Upcoming change to BillCharge findAllUserCharges API call
| Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy |
| ©2013 Google |