eric.frederich wrote:
I have a class which holds a connection to a server and a bunch of
services.
In this class I have methods that need to work with that connection
and services.
Right now there are about 50 methods some of which can be quite long.
From an organizational standpoint, I'd like t
eric.frederich wrote:
I have a class which holds a connection to a server and a bunch of
services.
In this class I have methods that need to work with that connection
and services.
Right now there are about 50 methods some of which can be quite long.
From an organizational standpoint, I'd like
Yeah... it does seem like a God Object.
My reasoning for putting them all into one big class is that the class
has references to all the required resources, connections, and
services.
The other option would be to have a simple object called Session which
did nothing but login and hold those referen
On Nov 20, 8:14 am, "eric.frederich" wrote:
> I have a class which holds a connection to a server and a bunch of
> services.
> In this class I have methods that need to work with that connection
> and services.
>
> Right now there are about 50 methods some of which can be quite long.
> From an org
eric.frederich schrieb:
I have a class which holds a connection to a server and a bunch of
services.
In this class I have methods that need to work with that connection
and services.
Right now there are about 50 methods some of which can be quite long.
From an organizational standpoint, I'd like
I have a class which holds a connection to a server and a bunch of
services.
In this class I have methods that need to work with that connection
and services.
Right now there are about 50 methods some of which can be quite long.
>From an organizational standpoint, I'd like to have method
implement
