[appengine-java] Is the native API really so much faster than JDO and slim3?
I'm looking at this online demo: http://slim3demo.appspot.com/performance/ Sample run: The number of entities: 1 low-level API:get: 2 millis Slim3: 2490 millis JDO: 6030 millis Is the low-level API really that much faster? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Is the native API really so much faster than JDO and slim3?
The low-level API does indeed look very fast. Just a comment on JDO: repeat runs roughly halve the JDO run time. I presume that this is because for repeat runs the JDO persistence manager factory has already been constructed. On Jun 6, 8:44 pm, DennisP wrote: > I'm looking at this online demo:http://slim3demo.appspot.com/performance/ > > Sample run: > The number of entities: 1 > low-level API:get: 2 millis > Slim3: 2490 millis > JDO: 6030 millis > > Is the low-level API really that much faster? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Channel API (Java) doesn't work locally, but in production mode.
Are you all using GWT? Any chance you can include some debug logs that include a request to / _ah/channel/dev/.*? And also log the token that's returned from ChannelService.CreateChannel? Thanks- -Moishe -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Stop blob URL from expiring
You can create the form without the generated upload url, and before submitting that form, perform an ajax call to generate an upload url at that time, with the callback setting the form's action, and submitting it. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/clB6T0cyd25kWW9K. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Secure Data Connector Spring
Hi, Is it possible to use the Spring REST API's with the Secure Data Connector e.g. RestTemplate or am I forced to use the URLFetch directly? I read somewhere that AppEngine will still use the secure data connector but I wondered if someone could confirm this to me. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/S0JhNFYyS3laNmtK. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Request was aborted after waiting too long to attempt to service your request.
Hello everyone, i am running a java REST service in the appengine and get this: "Request was aborted after waiting too long to attempt to service your request. This may happen sporadically when the App Engine serving cluster is under unexpectedly high or uneven load. If you see this message frequently, please contact the App Engine team." I see this message frequently and customer requests fail because of it. Can anyone help me please! Thanks a lot. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/X3E4cnhhblA3Z3dK. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Not able to commit changes to google code, eclipse plugin keep asking for password even if I am already logged in.
older version used to work fine for me ... is there any way to downgrade to older version ? On Mon, Jun 6, 2011 at 12:32 PM, Prashant wrote: > anyone ? > > On Mon, Jun 6, 2011 at 12:39 AM, Prashant wrote: > >> Hi, >> >> Since last eclipse plugin update (few days back) I am not able to commit >> changes to Google Code. If am logged in on eclipse it can deploy application >> to GAE but if I try to commit changes to Google Code, it will keep asking >> for password again and again. Any idea what's wrong ? >> >> Thanks, >> Prashant >> > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: LifecycleManager javadoc
On Sunday, June 5, 2011 2:32:57 AM UTC-7, radzish wrote: > Hi, > > Backends Overview page: > > http://code.google.com/appengine/docs/java/backends/overview.html > > Briefly explains how to use LifecycleManager. Therefore, reference to its > javadoc > > > http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/LifecycleManager.html > > does not work for me: 404 error code. > Thanks for the bug report, we're fixing it. > Where I can explanation to LifecycleManager and what else it can be used > for ? > > My specific questions: > > 1. does com.google.appengine.api.LifecycleManager.beginShutdown(long > deadline) method called from within backend makes backend to shut down. Is > that guaranteed > That method is only used internally and for testing. A backend instance can't shut itself down just yet. In the future, we plan to offer a way for a Backend instance to request shutdown. > 2. does LifecycleManager works for regular dynamic non-backend instance? > Especially I would like to know if I can use ShutdownHook to flush some > instance data to the datastore. > No. The shutdown process is currently only available for Backends. - Justin -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/U2FJWFA2OFpJMVFK. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Lots of 500 errors
I am using the URLFetchService low level api (which works great, esp Futures). I checked my dependencies for commons-httpclient but I didn't find any... I do have commons-fileupload, commons-lang, commons-logging from apache... as well as aopalliance, log4j and a bunch of springframework jars. I'm also packaging org.json libraries, but I plan to move to the repackaged version offered by GAE. Anyways, my appspot seems to be working this morning... so I thank the cloud masters at GAE :) -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/ZW1TaFF2VDEtRGdK. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: Short-lived timer
Another possibility could be to lazily calculate turns. When a user has either a rich client or web browser open, it pings the server every N seconds. The server then evaluates whether it's a new turn or not and does the computations at this time. If M turns have passed, the server runs the game through M iterations to "catch up" the game. Depending on what you're doing, this may be a slightly better implementation. Eager updating has the tradeoff of not scaling well, as the amount of work is linearly dependent on the number of games. Lazy evaluation has the benefit of scaling linearly as a function of the number of *active* games (many games will be abandoned), and, you can also "collapse" RPC calls to the datastore into a single call instead of repeatedly making them every N seconds. For instance: let's say you need to save game state each time. Over 10 minutes, you have to make 30 saves per game if you update every 20 seconds. If it's possible to collapse updating of game state lazily, if a user logs out and logs back in 10 minutes later, you can read the game state, run it through 10 minutes worth of iterations, and resave it - you've just improved your throughput in that scenario by a factor of 30, since in-memory local computations are incredibly cheap relative to off machine RPCs. One of the best practices of building App Engine is to minimize RPCs since these are the most expensive parts of your system. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Tue, Jun 7, 2011 at 3:26 AM, Ian Marshall wrote: > Would queued tasks in general, and deferred tasks in particular, suit > you? You can set an ETA for these tasks, and GAE/J guarantees not to > fire these tasks before any ETA set. > > You could use a scheduled task for a "heartbeat" of interval 1 minute, > and use this to enqueue tasks for ETAs such that you could have queued > task "heartbeats" as desired between your 1 minute scheduled task > "heartbeats". > > > On Jun 4, 4:07 am, Weston Pace wrote: > > I'm working on an interactive game. I was hoping for turns to be on > > the order of 20 seconds or less. It appears the cron framework can > > only schedule things in 1-minute intervals. Is there any method for > > shorter timers in GAE? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] share libraries between application
Yes, but locally, you should still add the files to your WEB-INF/lib directory. When you upload files, we hash the contents and check the signature against other files already uploaded so you only upload files that changed. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Mon, Jun 6, 2011 at 10:45 PM, ashwin menkudle wrote: > recently i am working with richfaces and spring. > to upload same libraries for every project is not great approach. > so can we share these jar files once which we had uploaded for some > project. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine-java/-/Tmk4cTVYZ3g0b29K. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] common reasons for compile jsp error
My app runs locally, but when I go to deploy to GAE I get an compile jsp error at line -1. I'm not doing anything fancy. Is there a do and don'ts for jsp in GAE which I can check my code against? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: Can't create application - SMS says account already verified
Just fill out that form and put your name in the comments. That form is effectively a "manual whitelisting request" for us. We go through each of the requests and approve them. It just has a longer turnaround time. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Sat, Jun 4, 2011 at 12:49 PM, Nichole wrote: > Google Voice? > > On Jun 3, 3:01 pm, Ronoaldo José de Lana Pereira > wrote: > > Sorry Joe, I don't know if you can unregister your phone number. I didn't > > found this kind of option. Ikai, any tips? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Request was aborted after waiting too long to attempt to service your request.
You get this error when your request waits in a pending queue. App Engine apps are autoscaled IF they can average under 1000ms. If they cannot, we do not give you additional instances, and requests line up in a pending queue. If your request waits in the pending queue for more than N seconds (I think N is 9 at the moment but I don't know for sure off the top of my head), this message is returned. You'll need to look at the average latency and figure out how to drop it to under 1000ms. Alternatively, if you enable concurrent Java requests, it'll be a higher ceiling before this error appears if you have "Always On" since you can serve a total of 3 (always on instances) * M (concurrency factor, I think this is 40 at the moment) requests at one time without requiring autoscaling. Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine On Wed, Jun 8, 2011 at 1:06 AM, holger wrote: > > Hello everyone, > > > > i am running a java REST service in the appengine and get this: > > > "Request was aborted after waiting too long to attempt to service your > request. This may happen sporadically when the App Engine serving cluster is > under unexpectedly high or uneven load. If you see this message frequently, > please contact the App Engine team." > > > > I see this message frequently and customer requests fail because of it. Can > anyone help me please! Thanks a lot. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine-java/-/X3E4cnhhblA3Z3dK. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] DLL how to handle data "tables"
I'm coming from a strong c# background. I'm used to visually designing my tables in SSMS then having VS create the data logic. I obviously see the greater flexibility of the way data is handled in appengine. I'm used to a strongly typed dataset, how can I achieve this in java for use with appengine? I guess I should say I plan on using the ENtity object to store data. not sure if I don't like the idea of using a string every time I access the entity. I believe it can leave room for error. I plan on creating an enum and each entry in the enum could be converted to string and access the entity. Some things I considered: 1. use properties to get/set the entity values then I find out there is no property support in java 2. extend a class, that contains basic data logic, for each entity type. Then I lose my strong typing. 3. mixture of one and two using methods where i cant use properties to get/set the values What are other people doing? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/Y3pkMnFlaExOUDBK. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Request was aborted after waiting too long to attempt to service your request.
Hello Ikai, thanks a lot for clearing that up! I will test my app with concurrent threads and try it. This was on my todo list anyway. ;-) However, the funny thing is that its latency averages at about 150ms. If i am not able to figure it out, i'll be back here. Thanks again, Holger On Wed, Jun 8, 2011 at 3:41 AM, Ikai Lan (Google) wrote: > You get this error when your request waits in a pending queue. > > App Engine apps are autoscaled IF they can average under 1000ms. If they > cannot, we do not give you additional instances, and requests line up in a > pending queue. If your request waits in the pending queue for more than N > seconds (I think N is 9 at the moment but I don't know for sure off the top > of my head), this message is returned. > > You'll need to look at the average latency and figure out how to drop it to > under 1000ms. Alternatively, if you enable concurrent Java requests, it'll > be a higher ceiling before this error appears if you have "Always On" since > you can serve a total of 3 (always on instances) * M (concurrency factor, I > think this is 40 at the moment) requests at one time without requiring > autoscaling. > > Ikai Lan > Developer Programs Engineer, Google App Engine > Blog: http://googleappengine.blogspot.com > Twitter: http://twitter.com/app_engine > Reddit: http://www.reddit.com/r/appengine > > > > On Wed, Jun 8, 2011 at 1:06 AM, holger wrote: > >> Hello everyone, >> >> >> i am running a java REST service in the appengine and get this: >> >> "Request was aborted after waiting too long to attempt to service your >> request. This may happen sporadically when the App Engine serving cluster is >> under unexpectedly high or uneven load. If you see this message frequently, >> please contact the App Engine team." >> >> >> I see this message frequently and customer requests fail because of it. Can >> anyone help me please! Thanks a lot. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine for Java" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/google-appengine-java/-/X3E4cnhhblA3Z3dK. >> To post to this group, send email to >> google-appengine-java@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine-java+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine-java?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- Holger Weissböck hol...@gamua.com http://gamua.com http://www.sparrow-framework.org -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Request was aborted after waiting too long to attempt to service your request.
Is this documented anywhere? It's something I figured out from occasional comments I've seen on this list over the years, but I've never seen it mentioned in the official documentation. And it's kinda important. In particular, I'd like to know what the bounds are for threaded java, and how the average time is computed - is it mean, median, or mode? I have a GWT app that takes one major hit at startup (possibly seconds) and then performs lots of smaller hits as the user interacts with the app. It would be nice to know if this will cause problems down the road... Jeff On Tue, Jun 7, 2011 at 6:41 PM, Ikai Lan (Google) wrote: > You get this error when your request waits in a pending queue. > App Engine apps are autoscaled IF they can average under 1000ms. If they > cannot, we do not give you additional instances, and requests line up in a > pending queue. If your request waits in the pending queue for more than N > seconds (I think N is 9 at the moment but I don't know for sure off the top > of my head), this message is returned. > You'll need to look at the average latency and figure out how to drop it to > under 1000ms. Alternatively, if you enable concurrent Java requests, it'll > be a higher ceiling before this error appears if you have "Always On" since > you can serve a total of 3 (always on instances) * M (concurrency factor, I > think this is 40 at the moment) requests at one time without requiring > autoscaling. > Ikai Lan > Developer Programs Engineer, Google App Engine > Blog: http://googleappengine.blogspot.com > Twitter: http://twitter.com/app_engine > Reddit: http://www.reddit.com/r/appengine > > > On Wed, Jun 8, 2011 at 1:06 AM, holger wrote: >> >> Hello everyone, >> >> >> i am running a java REST service in the appengine and get this: >> >> "Request was aborted after waiting too long to attempt to service your >> request. This may happen sporadically when the App Engine serving cluster is >> under unexpectedly high or uneven load. If you see this message frequently, >> please contact the App Engine team." >> >> >> I see this message frequently and customer requests fail because of it. >> Can anyone help me please! Thanks a lot. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine for Java" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/google-appengine-java/-/X3E4cnhhblA3Z3dK. >> To post to this group, send email to >> google-appengine-java@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine-java+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine-java?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: New GWT/App Engine site
I find it fast enough. May be you logged-in on a peak of traffic? if you have the chance try again and let us know please ;-) On May 31, 7:00 pm, Jay Young wrote: > Cool idea, but I think you might want to look into GWT's code splitting. It > took me 35 seconds to download your 2.11MB file. That's going to turn off a > LOT of users. I understand that that file gets cached, but that's not going > to be the case on their first trip to your site. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: R: Re: New GWT/App Engine site
Hi Jeff, 1) Polishing the navigation, as you said, it kind thought with GWT, but I absolutely agree with you that it needs to be improved... already some changes have been done, but going back at the same position & level on the map is just a mystery ;-) 2) I did not quite understand well what do you mean in "just pick a random sample"... Are you suggesting to load a pre-configured map/kml with some markers? On May 31, 11:12 pm, Jeff Schnitzer wrote: > Nice looking site... just on casual perusal, two things jumped out at me: > > 1) Polish the navigation a bit more. For example, you zoom into the > map, click on a trail, click through to the trail's page, then hit the > browser back button (seems to be the only way to get back) - and > you're now zoomed out at the top level rather than being back where > you were before you clicked through to the trail's page. There were a > few things like this I noticed. This is the stuff in GWT that is hard > to get right but it's critical if you want the site to be useable. > > 2) When looking at the world-view, add a few pins from the collection. > I shouldn't have to zoom a couple times to see any content. The map > starts out looking empty and boring... if you don't want to include > all, just pick a random sample so that it looks intriguing. > > Jeff > > > > > > > > On Tue, May 31, 2011 at 11:44 AM, ale wrote: > > You're right ... > > It will be one of the first things to improve ... > > Thanks a lot! > > > Alessandro > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine for Java" group. > > To post to this group, send email to google-appengine-java@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine-java+unsubscr...@googlegroups.com. > > For more options, visit this group at > >http://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
