AppEngine 1.3.0
1 view
Skip to first unread message
George Moschovitis
Dec 15, 2009, 11:46:47 AM12/15/09
to nitro-devel
Great news,
the new AppEngine 1.3.0 seems to be considerably faster with Rhino
(and appenginejs)
-g.
the new AppEngine 1.3.0 seems to be considerably faster with Rhino
(and appenginejs)
-g.
Roberto Saccon
Dec 15, 2009, 1:43:59 PM12/15/09
to nitro-devel
Cool !
what a pity that uploaded large blobs can't be processed in any way
yet (for urlfetch-based action they will be too large anyway).
--
Roberto
On Dec 15, 1:46 pm, George Moschovitis <george.moschovi...@gmail.com>
wrote:
what a pity that uploaded large blobs can't be processed in any way
yet (for urlfetch-based action they will be too large anyway).
--
Roberto
On Dec 15, 1:46 pm, George Moschovitis <george.moschovi...@gmail.com>
wrote:
Robin B
Dec 18, 2009, 6:23:31 PM12/18/09
to nitro-devel
> what a pity that uploaded large blobs can't be processed in any way
> yet (for urlfetch-based action they will be too large anyway).
> yet (for urlfetch-based action they will be too large anyway).
Exactly, I was really hoping the large file support was going to be
like S3, only better, but it is not even close.
Since large file support is a GAE API, it creates an unnecessary GAE
lock-in. Large file support should have been implemented as a
standalone HTTP web service like S3.
Oh well, one can always use S3, but more competition for S3 would have
been great.
Robin
On Dec 15, 12:43 pm, Roberto Saccon <rsac...@gmail.com> wrote:
> Cool !
George Moschovitis
Dec 19, 2009, 3:29:59 AM12/19/09
to nitro...@googlegroups.com
On Sat, Dec 19, 2009 at 1:23 AM, Robin B <rob...@gmail.com> wrote:
> what a pity that uploaded large blobs can't be processed in any way
> yet (for urlfetch-based action they will be too large anyway).
After a closer inspection, the Image API is extended to create images straight from the blobstore.
However, I am not sure how one can store the images back to the blobstore.
-g.
Exactly, I was really hoping the large file support was going to be
like S3, only better, but it is not even close.
Since large file support is a GAE API, it creates an unnecessary GAE
lock-in. Large file support should have been implemented as a
standalone HTTP web service like S3.
Oh well, one can always use S3, but more competition for S3 would have
been great.
Robin
On Dec 15, 12:43 pm, Roberto Saccon <rsac...@gmail.com> wrote:
> Cool !
>
> --
> Roberto
>
> On Dec 15, 1:46 pm, George Moschovitis <george.moschovi...@gmail.com>
> wrote:
>
> > Great news,
>
> > the new AppEngine 1.3.0 seems to be considerably faster with Rhino
> > (and appenginejs)
>
> > -g.
--
You received this message because you are subscribed to the Google Groups "nitro-devel" group.
To post to this group, send email to nitro...@googlegroups.com.
To unsubscribe from this group, send email to nitro-devel...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nitro-devel?hl=en.
--
blog.gmosx.com
Roberto Saccon
Dec 19, 2009, 8:20:29 AM12/19/09
to nitro-devel
I think they the images after transformation are to be stored in the
datastore, and because this only works when they become less than 1
MB, they only transformation one can use on blobstore images is down-
sizing (creating thumbnails).
datastore, and because this only works when they become less than 1
MB, they only transformation one can use on blobstore images is down-
sizing (creating thumbnails).
--
Roberto
On Dec 19, 5:29 am, George Moschovitis <george-moschovi...@gmosx.com>
wrote:
> > nitro-devel...@googlegroups.com<nitro-devel%2Bunsubscribe@googlegr oups.com>
Reply all
Reply to author
Forward
0 new messages