.net - Facade design pattern with states -


after implementing facade hide complex sub systems, end having single class client. problem single class still has on 100 apis. seems against cohesive principle. facade class manages states objects used among sub systems can hided. system consist of sub-systems(e.g. project, policy, user, permissions etc) think might able design facade in more modular way. design patterns may work facade in case?

as say, having more 100 apis in 1 class not idea. can split different facade classes. common functionality can moved base classes. not design pattern core of oo. state can still maintained. not sure if using session store save state. if can still continue so.

you can use cache store state or use database. if using ejbs sfsb provides functionality.


Comments

Popular posts from this blog

c# - Send Image in Json : 400 Bad request -

jquery - Fancybox - apply a function to several elements -

An easy way to program an Android keyboard layout app -