I don't think I've ever sealed a class before...would there be any benefit to sealing a public class that contains fields for a server to process? The object is sent over a network socket to the server, the server reads the data in the object and responds accordingly.
I read sealed (C# Reference) at MSDN, and at the bottom it says:
To determine whether to seal a class, method, or property, you should generally consider the following two points:
- The potential benefits that deriving classes might gain through the ability to customize your class.
- The potential that deriving classes could modify your classes in such a way that they would no longer work correctly or as expected.
I would say no class would ever NEED to derive from the class, any added data would be ignored by the server because it wouldn't know to look for it. The second though...I'm not sure about. Anyone know of any security concerns or issues that I should possibly consider with this?
I'd really appreciate any feedback :)