If you call NetClient.Disconnect function, it starts arranging currently using resources(thread and other objects) internally.

In case of calling NetClient.FrameMove function on separated thread, you must not use Thread.Abort 함수 on the thread which is performing FrameMove.

We recommend to finish thread using separate finishing Flag variable.

You must call Dispose function explicitly when deleting NetClient/NetSever object.

Releasing resource(Deleting Native RmiStub, RmiProxy object) on RmiStub, RmiProxy which was Attach when calling NetClient/NetServer.Dispose function is done at the same time.

When building new NetClient/NetServer object after calling NetClient/NetServer.Dispose function, you must newly build and process Attach on RmiProxy object.