I am currently porting caerusone <http://caerusone.googlecode.com/files/caerusone.pdf>to Google app engine and so far has been successful to be able to run generic mapper / graph in cloud and has been able to rapidly prototype application on Google app engine infrastructure.
A Demo <http://caerusone.appspot.com/site/wide_5678/wide.html.jsp>is available at Following location<http://caerusone.appspot.com/site/wide_5678/wide.html.jsp> To see different graphs possible to run choose "file"->"open graph" and select any graph. I am facing following problems while porting workflow: 1) What is the best way to make sure a long running java class with static variables will not get persisted. 2) Since my workflow definition could become sizable what is the best way to keep in memory seems from document there is no guaranteed way of doing it.? 3) From documents it seems backend is the only way to go for implementing workflow? is there a way i can get a free backend to port application ? P.S When workflow definition is in memory it is either camel process or a java object representing a workflow/graph. thanks and regards, sumit -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/54-oNMleHZcJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
