Re: [google-appengine] Re: Open Source Apps for GAE

2015-05-30 Thread Jacob Gadikian
What are your thoughts on other applications?

-Jake

Jacob Gadikian
E-mail: fad...@gmail.com
SKYPE: faddat
Phone/SMS: +86 186-2612-6079


On Wed, May 27, 2015 at 4:00 PM, Nick (Cloud Platform Support) <
pay...@google.com> wrote:

> Looks to be promising. I think you might want to reach out to some other
> developers in the community (through github, even through something like
> reddit.com/r/webdev (?)) to get submissions and grow the list.
>
> Generally, the status of whether something runs unmodified on App Engine
> can be quite complex, as it can mean that most features but one or two
> work, for example. In addition, with the development of Managed VMs and
> custom runtimes ,
> pretty much everything can now run on "App Engine" :)
>
> Best wishes,
>
> Nick
>
>
> On Tuesday, May 26, 2015 at 2:52:41 AM UTC-4, Jacob Gadikian wrote:
>>
>> http://awesome-appengine.netlify.com/
>>
>> There we go!  Used github+netlify.com
>> 
>> to do it.  Too about an hour total.  Please submit pull requests to
>> http://github.com/kloudsio/awesome-appengine/
>>
>> Jacob Gadikian
>> E-mail: fad...@gmail.com
>> SKYPE: faddat
>> Phone/SMS: +86 186-2612-6079
>>
>>
>> On Tue, May 26, 2015 at 5:55 AM, Jacob Gadikian  wrote:
>>
>>> I was going to do netlify but really I am still learning GAE.
>>>
>>> I may try this out:
>>>
>>> https://github.com/nimbus154/OratoricalDecaf/tree/master/Project
>>>
>>> and see if it can be used for our purposes.
>>>
>>> -Jake
>>>
>>>
>>> Jacob Gadikian
>>> E-mail: fad...@gmail.com
>>> SKYPE: faddat
>>> Phone/SMS: +86 186-2612-6079
>>>
>>>
>>> On Tue, May 26, 2015 at 4:56 AM, Jacob Gadikian 
>>> wrote:
>>>
 I do open source webapps for a living-- now that I think about it, I
 should make this into something like staticgen.com.  Something tells
 me that their code just might be open source, making a fork of that site
 relatively painless

 Best,

 -Jake

 Jacob Gadikian
 E-mail: fad...@gmail.com
 SKYPE: faddat
 Phone/SMS: +86 186-2612-6079


 On Tue, May 26, 2015 at 4:53 AM, Jacob Gadikian 
 wrote:

> https://github.com/faddat/awesome-appengine
>
> Jacob Gadikian
> E-mail: fad...@gmail.com
> SKYPE: faddat
> Phone/SMS: +86 186-2612-6079
>
>
> On Tue, May 26, 2015 at 4:50 AM, Jacob Gadikian 
> wrote:
>
>> That is a great idea.  GH going up now-- thanks!
>>
>> -Jake
>>
>>
>> Jacob Gadikian
>> E-mail: fad...@gmail.com
>> SKYPE: faddat
>> Phone/SMS: +86 186-2612-6079
>>
>>
>> On Tue, May 26, 2015 at 3:56 AM, Nick (Cloud Platform Support) <
>> pay...@google.com> wrote:
>>
>>> This is a great idea, and look forward to it developing.
>>>
>>> I feel it would be better to make it a website with a contact link
>>> rather than a "quip" doc, especially since anybody can access a website
>>> while this "quip" service doesn't even implement OpenID connect, forcing
>>> users to create an account and password with them.
>>>
>>> Nonetheless, this is a great initiative and I encourage you to
>>> publicize it. Perhaps manage updates to the list via a github 
>>> repository?
>>> This leaves a natural place for discussions (the "issues" page) about
>>> whether issues come up with this or that open source project's
>>> compatibility, or candidate projects for review.
>>>
>>> --
>>> You received this message because you are subscribed to a topic in
>>> the Google Groups "Google App Engine" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/google-appengine/RiUpCdNaB6U/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> google-appengine+unsubscr...@googlegroups.com.
>>> To post to this group, send email to
>>> google-appengine@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/google-appengine.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-appengine/e301e183-26b1-469a-9267-48cb681d42dc%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>

>>>
>>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/RiUpCdNaB6U/unsubscribe
> .
> To unsubscribe from this group and all its

[google-appengine] Building an Android Application with Google App Engine

2015-05-30 Thread Joe Seph


Hello guys,
so currently, we are building a mobile  social network application where 
users will be able to upload and view Pictures and Musics files.
we have 2 scenarios in order to implement the GAE with our android 
application and backend control panel. 
- First scenario is to implement the GAE PHP with our application backend 
and let the backend handle all the APIS requests from the mobile side and 
handle them with the GAE but for in case i need to upload a certain image 
to the GAE I will need to encode the image to base64 and decode it on the 
server and then upload it into the GAE and then wait until the upload 
process finishes and return the Reference to the backend then update the 
status on the mobile side as you can notice this scenario will cost me a 
lot of time and the quality of the image will be dropped due to encoding 
and decoding .



- Second scenario is to implement the GAE Directly to the android side and 
let it upload files(Jpg,mp3) directly to the GAE (No need for Base64) and 
then send the references from GAE to the mobile side in order to be sent to 
Backend to be saved in the database .



I'm not sure if the GAE works with android to achieve the second scenario 
as it will be best solution which will decrease time and will bypass 
decoding and encoding Process. 

so what do you guys think about the above solutions and what is the best 
optimized and efficient solution in your opinion?

thanks ,

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/217092b4-d2f8-4d6a-8ab9-cec88898d053%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [google-appengine] Building an Android Application with Google App Engine

2015-05-30 Thread Karl MacMillan
  

> On May 30, 2015, at 10:57 AM, Joe Seph  wrote:
> 
> 
> Hello guys,
> 
> so currently, we are building a mobile  social network application where 
> users will be able to upload and view Pictures and Musics files.
> we have 2 scenarios in order to implement the GAE with our android 
> application and backend control panel. 
> - First scenario is to implement the GAE PHP with our application backend and 
> let the backend handle all the APIS requests from the mobile side and handle 
> them with the GAE but for in case i need to upload a certain image to the GAE 
> I will need to encode the image to base64 and decode it on the server and 
> then upload it into the GAE and then wait until the upload process finishes 
> and return the Reference to the backend then update the status on the mobile 
> side
> 
> 

I’m a little confused about what you mean by GAE and how that might be 
different from the PHP backend. I’m getting a sense that you mean something 
specific here but are using the terms in a different way than is usually used, 
which is making it hard to answer your question.


I also wonder if you are making this harder than it needs to be. A typical 
approach that people use for uploading data is to simply expose a HTTP endpoint 
that the mobile application can POST to with the image data (perhaps as 
multipart form data) and then if they need to return some sort of handle or 
metadata they simply do that in the response. It’s only one round-trip then.


If you are running PHP on Google App Engine, the handler for that HTTP endpoint 
can then put the data wherever. I would suggest storing it in Google Cloud 
Storage and, if helpful, storing some meta-data about the data in the Datastore.


>  as you can notice this scenario will cost me a lot of time and the quality 
> of the image will be dropped due to encoding and decoding .
> 
> 
> 
> 

I’m a little confused about the concern over image quality. Base64 encoding 
does not impact image quality - it is simply an encoding of binary data and is 
lossless (http://en.wikipedia.org/wiki/Base64).


I hope this helps - again, it’s a little hard to understand your question or 
concerns. If I could suggest, it might help if you spend a little more time 
with the App Engine documentation. That might help you answer your own 
questions and it will likely help you ask questions using the terminology from 
the documentation, making it easier for others to help you.


Karl

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8FD067B6-F2B9-4D5C-B3C8-92CB66CB1B52%40rakkoon.com.
For more options, visit https://groups.google.com/d/optout.