Client ----- Engine ------ Java Classes ------ Server
In "Java classes" module I have the two public classess public class A and public class B
my client can access class A throuhg engine but at the same time I dont want to give the access of public clas B to the client. in this case I could think making class B as private/protected but I can not do this because In my server module I need object of Class B thats the root cause of making these classes public
I am thinkning about the following solutions 1. add the key in these clasess and give the access to these classes depending upon the key thay client is passing - but it requried lots of code changes
You can introduce a layer of public objects that hides a layer of private objects.
This doesn't prevent a Client coder from using the ServerAPI unless you can somehow avoid distributing the ServerAPI class to the client team.
It's a little odd to have both client and server depending on JavaClasses. It might be a global framework, a case of really cool Dependency Inversion or a case of circular dependencies. Why does that happen? [ December 22, 2005: Message edited by: Stan James ]
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Anderson gave himself the promotion. So I gave myself this tiny ad: