[appengine-java] Re: RPC call and variables
It is a clustered environment and you cannot assume that every request is run in the JVM. If you want to share data between requests you should persist them (data) in datastore. --~--~-~--~~~---~--~~ 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: RPC call and variables
There are two ways. To use a GAE datastore service. Or to use some external service to store that value there - especially when you need Comet or something like that. On Sep 15, 6:50 pm, leszek wrote: > It is a clustered environment and you cannot assume that every request > is run in the JVM. If you want to share data between requests you > should persist them (data) in datastore. --~--~-~--~~~---~--~~ 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: RPC call and variables
Hello Thanks leszek and Bulat for your reply I am learning datastore service and then would try to solve my problem through it. But I would like to know more about "external service to store variables". I need comet like feature in my application. My application would require many such calls and since there is a limit on datastore calls, external service to store variables could be a good alternative. Regards Sahil Mahajan On Sep 16, 7:03 am, Bulat Sirazetdinov wrote: > There are two ways. To use a GAE datastore service. Or to use some > external service to store that value there - especially when you need > Comet or something like that. > > On Sep 15, 6:50 pm, leszek wrote: > > > It is a clustered environment and you cannot assume that every request > > is run in the JVM. If you want to share data between requests you > > should persist them (data) in datastore. --~--~-~--~~~---~--~~ 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: RPC call and variables
Follow this thread - could be helpful http://groups.google.co.uk/group/google-appengine-java/browse_frm/thread/d816992c5a82506b/e50b4eb988d2f45b?lnk=gst&q=comet#e50b4eb988d2f45b --~--~-~--~~~---~--~~ 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: RPC call and variables
Hello Thanks leszek I tried datastore, it has solved many of my problems. Though I am not getting exact results, but I feel if I spend more time, I may improve the problems. I receive following message in my info log after certain intervals. org.datanucleus.ObjectManagerImpl close: Outstanding nontx update being committed to datastore I found http://groups.google.com/group/google-appengine-java/browse_thread/thread/8c8d3191d287553f information on this topic. I would like to know more about this. I have started looking into XMPP API which is specified in the link given by you. I would also like to know about any other alternative? Regards Sahil Mahajan On Sep 16, 2:37 pm, leszek wrote: > Follow this thread - could be helpful > > http://groups.google.co.uk/group/google-appengine-java/browse_frm/thr... --~--~-~--~~~---~--~~ 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: RPC call and variables
Hi Sahil. It sounds like you can get rid of this particular log message by performing all your writes inside of a transaction. If you don't need or want to use transactions, then you can safely ignore this particular info log message. - Jason On Thu, Sep 17, 2009 at 9:06 PM, Sahil Mahajan wrote: > > Hello > Thanks leszek > > I tried datastore, it has solved many of my problems. Though I am not > getting exact results, but I feel if I spend more time, I may improve > the problems. > > I receive following message in my info log after certain intervals. > org.datanucleus.ObjectManagerImpl close: Outstanding nontx update > being committed to datastore > > I found > http://groups.google.com/group/google-appengine-java/browse_thread/thread/8c8d3191d287553f > information on this topic. I would like to know more about this. > > I have started looking into XMPP API which is specified in the link > given by you. > I would also like to know about any other alternative? > > Regards > Sahil Mahajan > > On Sep 16, 2:37 pm, leszek wrote: > > Follow this thread - could be helpful > > > > http://groups.google.co.uk/group/google-appengine-java/browse_frm/thr... > > > --~--~-~--~~~---~--~~ 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: RPC call and variables
Thanks Jason I used Transactions and now I don't see that message in my info log. Regards Sahil On Sep 18, 11:49 pm, "Jason (Google)" wrote: > Hi Sahil. It sounds like you can get rid of this particular log message by > performing all your writes inside of a transaction. If you don't need or > want to use transactions, then you can safely ignore this particular info > log message. > - Jason > > On Thu, Sep 17, 2009 at 9:06 PM, Sahil Mahajan wrote: > > > Hello > > Thanks leszek > > > I tried datastore, it has solved many of my problems. Though I am not > > getting exact results, but I feel if I spend more time, I may improve > > the problems. > > > I receive following message in my info log after certain intervals. > > org.datanucleus.ObjectManagerImpl close: Outstanding nontx update > > being committed to datastore > > > I found > >http://groups.google.com/group/google-appengine-java/browse_thread/th... > > information on this topic. I would like to know more about this. > > > I have started looking into XMPP API which is specified in the link > > given by you. > > I would also like to know about any other alternative? > > > Regards > > Sahil Mahajan > > > On Sep 16, 2:37 pm, leszek wrote: > > > Follow this thread - could be helpful > > > >http://groups.google.co.uk/group/google-appengine-java/browse_frm/thr... --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
