Shorter naming convention for types

Question

I am developing a framework, and some of the objects have reaaally long names. I don't really like this, but I don't like acronyms either. I am trying to come up with a shorter name for "EventModelSocket", basically a wrapper around the .Net socket class that implements various events, and methods to send files, objects, etc. Some of the objects have really long names due to this, such as "EventModelSocketObjectReceivedEventArgs" for example.

I've tried everything from a thesaurus, to a dictionary to sitting here for hours thinking.

When you come upon situations like this, what is the best way to name something?

Answer 1

Push some of it into the namespace.

For example:

EventModelSocketObjectReceivedEventArgs

becomes

EventModel.Sockets.ReceivedEventArgs