How many IDL files are needed when there are multiple components in a distributed system? -
This is the scenario.
There are three components, A, B and C.
The components of component A component can be used using B-component B component A and component C methods. Components can use C component B.
How many IDL files are needed to implement this scenario? How many stubs and skeletons are needed?
I was thinking of four IDL files but do we have many slates and skeletons?
Methods based on the size of your services / components), I have them based on the number of those computers I will try to split into different rational units that you want to connect.
For example, it can understand the two different services implemented by the same server: one for internal purposes and which is to be published or a service is divided into two parts because These two parts are not really logically united, though for some reason implemented by the same component. All these services can be shared or the same IDL file can be shared.
If you still want to reduce the amount of files, then at least, keep in mind that announcement, publication and a certain service interface does not mean that a given component is applicable to the service It is necessary to be able to access the service, use the service or have permission to call it.
Comments
Post a Comment