Which design pattern is used for session design pattern?

Question

1.00/5 (2 votes)

See more:

, +

I Have got two answers for the internet Singleton and Factory design pattern? Which should we use? Both of them? and Why?

What I have tried:

I Have got two answers for the internet Singleton and Factory design pattern?

Posted 27-Jun-21 22:04pm

Ishmeet Kaur

Updated 28-Jun-21 1:10am

Add a Solution

Comments

CHill60 28-Jun-21 4:16am

It might help if you describe your situation a little better. What are you trying to achieve

Richard MacCutchan 28-Jun-21 4:48am

Design patterns may be used to solve issues in your design. But you cannot decide which one to use before you have the design.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Greg Utas · Answer 1 · 2021-06-28T01:10:00

It's difficult to answer given the brevity of your question.

I wouldn't call a session a design pattern. It could be called a protocol pattern, but it's not a software pattern in the usual sense of the term. As a protocol pattern, it consists of a session establishment phase, ongoing communication phase, and session release phase. Some sessions have simple protocols, and some have complex ones. TCP and phone calls are examples of sessions that are familiar to most developers.

If we assume IP-based communication, a Service that has a session could be a singleton. If the system has more than one type of Service, each run-time instance of a Session (subclassed according to the Service that it supports) could be created using the Factory pattern. A Service might have State singletons and EventHandler singletons, although each State would probably be a Flyweight rather than a true singleton.