No problem. Don't give up on the AWS project just yet ;).
Al. jjbunn wrote: > Thanks Al! > > I took the precaution of asking Amazon for permission to use their Web > Services > before going any further with my application. > > Unhappily, they declined. So it looks like I will have to shelve the > idea, which is a pity. > Here is the text of what they sent me: > > "Hello Julian, > > Thank you for your recent inquiry about developing a mobile > application using Amazon Associates Web Services. At this time Amazon > is not generally allowing the use of Amazon Associates Web Services > for mobile device applications, and we are not prepared to approve > your request to develop the service you outline below. > > We thank you for your interest in Amazon. > > Regards, > > [name removed] > Amazon Web Services > http://aws.amazon.com"; > > As you may imagine, I'm a little disappointed. > > Julian > > > On Feb 24, 2:36 am, Al Sutton <a...@funkyandroid.com> wrote: > >> Yup, thats how it's done in AndAppStore. >> >> The "trickiest" bit is calculating the signature, but once you know what >> you've got to include, well, our method is about 30 lines of code and >> most of that is calls to StringBuilder.append(). Then we add all the >> relevant headers to the request and send it over using the HTTPClient >> libraries. >> >> Parsing the response is simple enough, we use a SAXParser, feed it a >> DefaultHandler derived class written to parse the response, and then >> pull the result from the DefaultHandler derived class. >> >> Al.http://andappstore.com/ >> >> >> >> jjbunn wrote: >> >>> Hello Al, >>> >>> Thanks for this sensible suggestion: so you are basically building the >>> request body yourself, sending it with HTTPClient, and then parsing >>> the response with your own software? >>> >>> Julian >>> >>> On Feb 23, 7:51 am, Al Sutton <a...@funkyandroid.com> wrote: >>> >>>> You don't need the whole AWS kit to do AWS things. You can use the >>>> HTTPClient libraries on the phone and a small amount of coding to write >>>> the stuff yourself. >>>> >>>> The AWS stuff we use in AndAppStore was written in-house and is less >>>> than 1500 lines and handles uploads, listing buckets, and deletions in >>>> S3 and distribution through CloudFront. >>>> >>>> Al. >>>> >>>> jjbunn wrote: >>>> >>>>> On Feb 22, 2:55 pm, "Mark Murphy" <mmur...@commonsware.com> wrote: >>>>> >>>>>>> Many thanks ... this sounds like a good plan. However, there are quite >>>>>>> a few >>>>>>> of them, ten in total. >>>>>>> >>>>>> 10 JARs? >>>>>> >>>>>> Which AWS service are you using? There has to be some Java client for it >>>>>> less pudgy than 10 JARs' worth. >>>>>> >>>>>>> Is there a way of converting the jars directly >>>>>>> rather than finding all the source and recompiling that, or should I >>>>>>> bite the bullet? >>>>>>> >>>>>> Well, you tried converting the JARs directly, which is what gave you your >>>>>> error. The point of recompiling from source is to avoid converting the >>>>>> JARs directly. >>>>>> >>>>>> Case in point: the stock Beanshell JAR (www.beanshell.org) does not work >>>>>> on Android, because (I think) it was compiled with Java 1.4.2, and we >>>>>> need >>>>>> Java 1.5+. However, recompiling Beanshell to create a fresh JAR, with a >>>>>> current Java compiler, worked just fine. >>>>>> >>>>>> -- >>>>>> Mark Murphy (a Commons Guy)http://commonsware.com >>>>>> _The Busy Coder's Guide to Android Development_ Version 2.0 Available! >>>>>> >>>>> Amazonsupplies with their Java AWS kit a set of ten third party jars. >>>>> They are: >>>>> >>>>> commons-codec-1.3.jar >>>>> commons-httpclient-3.0.1.jar >>>>> commons-logging-1.1.jar >>>>> activation.jar >>>>> jaxb-all-deps.jar >>>>> jaxb-api.jar >>>>> jaxb-impl.jar >>>>> jaxb-xjc.jar >>>>> jsr173_1.0_api.jar >>>>> log4j-1.2.14.jar >>>>> >>>>> I did manage to find source for just about all of these (except >>>>> activation.jar) but am having a >>>>> devil of a game combining them all into my project: there seem to be >>>>> dependencies on e.g. >>>>> beans that are problematic. >>>>> >>>>> I'll keep plugging away at it. Thanks for the advice. >>>>> >>>> -- >>>> ====== >>>> Funky Android Limited is registered in England & Wales with the >>>> company number 6741909. The registered head office is Kemp House, >>>> 152-160 City Road, London, EC1V 2NX, UK. >>>> >>>> The views expressed in this email are those of the author and not >>>> necessarily those of Funky Android Limited, it's associates, or it's >>>> subsidiaries. >>>> >> -- >> ====== >> Funky Android Limited is registered in England & Wales with the >> company number 6741909. The registered head office is Kemp House, >> 152-160 City Road, London, EC1V 2NX, UK. >> >> The views expressed in this email are those of the author and not >> necessarily those of Funky Android Limited, it's associates, or it's >> subsidiaries. >> > > > -- * Written an Android App? - List it at http://andappstore.com/ * ====== Funky Android Limited is registered in England & Wales with the company number 6741909. The registered head office is Kemp House, 152-160 City Road, London, EC1V 2NX, UK. The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
