Dear All,

Thanks you all for the very fast reply .. I have tried to be short to 
describe the problem but may be too fast :-) ... 

Right now we have an application, written 100% in Java for both client and 
server side. Thanks to great GWT, the client side is converted to 
(offuscated) javascript..  Also with one click, we can deploy the 
application to run as AppEngine on Google Cloud .. The client side 
communicate with the server side with RPC ...  all Great stuff

Now the challenge: It is not exactly our situation, but imagine that we 
would like to give the possibility to partnering companies to make 
modification to the client side of the application and deploy such 
resulting application as their own ... For that we are willing to share the 
client code. 

As we need to make a living we would like to keep the full control of the 
server side and not provide the server side source code  ....   the 
partnering company "client" applications will have then to communicate with 
our master server application and a fee will be paid  on usage .. 

Thus the idea to split our application into two App Engine applications .. 
one in control of the partnering company and one in our control .. Of 
course the problem is that those 2 need to communicate .. 

Any suggestion,

B.

-- 
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/-/p--rlAL0klYJ.
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?hl=en.

Reply via email to