Hey Corinne,

+∞ to cookbook
+9001 to create server

We already discussed it here and several times at meetings[1]. This is on our roadmap. Summers started to develop POC[2], but stopped. Our idea was to use vert.x and make one "module" per feature isolated to use in cookbook and integration tests.

[1] http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-multipart-cookbook-component-td3553.html
[2] https://github.com/secondsun/aerogear-integration-tests-server

On Thu, Sep 19, 2013 at 4:42 AM, Corinne Krych <corinnekrych@gmail.com> wrote:
Hello Guys

I like very Android Cookbook repo and I like to start the same idea for iOS. Putting together receipes in one common repo with different exemples sorted by folder. Adaopting the naming convention "HowTo…." for the file name that will match the documentation "How to … " is a good ay to easily find the information you need.

Talking about it on IRC we had a question though: how do we handle when in the exemple you need a server side code.

Would you deploy it on cloud server and available for client apps. Like in https://github.com/aerogear/aerogear-android-cookbook/blob/master/src/org/jboss/aerogear/cookbook/pipeline/HowToUsePipeWithPagination.java#L58

Or would you package the server side exemple in the cookbook repo?
I rather put servide side in cookbook as we could also to demo this part too.

We have this need for example with the multipar file upload example:


aerogear-dev mailing list