I'm working on a RPC like service and I was wondering if I picked the right method to implement my classes that I'll be persisting to the datastore. Also note that I allow users to create their own keys used to lookup their data.
Currently I have a MerchantClass Entity that holds my merchants and a DataWrapper Entity that holds the data they are looking for. Several merchants could be making requests at the same time, and as I understand it could cause (read/write) transactions to fail. I don't have any relationships at the moment because I don't want opening a Transaction on the MerchantClass Entity to prevent read/writes to the DataWrapper Entities. However, I do want to limit the scope in a more modular way to keep a merchants transactions from interfering with other merchants transactions. My overall goal is speed if I just need to keep it simple. Currently I can get a merchant and verify their status, then get their requested transaction without any problems. But I merchants can't register two transactions with the same key, and I'm a little worried that one merchant could interfere with the success of another merchants successful transactions. Thanks for input! -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
