Strategy Pattern (Initial thoughts on a Client Server architecture)

Any client server application needs to pass requests and await responses between the client and server. Use of the Strategy Pattern, can do a good job here. So, I am thinking, keep the code neat, encaptulate the request code, request data and response processing in just one class. Abstract the server from adding, modifying new requests from client. Obvious benefit, the server need not be modified for new requests added by the client, and multiple developers working on the client code.

Anyone want to take up the challenge of designing such a architecture ?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s