Hello,

I am looking at two aspects in the JMeter codebase: RMI and serialization.

I don't believe I've ran into a document explaining the architecture
here, only documents explaining how to configure JMeter as an user.

So, about RMI, the way I see it you have two "channels":

* a control channel where the master starts/stops/provisions the slaves and
* a results channel where result data is streamed back (which is also
the most bandwidth intensive)

Is this correct? What other communications happen between the master and slave?

Regarding serialization: why is so much serialized?

I saw this line in RemoteStart

> testTree.add(testTree.getArray()[0], gui.getMainFrame());

and it makes no sense to me to serialize the main frame itself. Maybe
this is just done because MainFrame implements TestStateListener so
you actually just want to provide a TestStateListener?

I understand why you would send the model but why the whole GUI?

I feel there is some historic and architectural info I am missing
here. Where is the API boundary between the GUI, the model and the
engine?

--emi

Reply via email to