求教：Facade Pattern vs Static Variable - 未名空间MITBBS历史存档

国际科技财经博客移民网络热点娱乐民生时事公众号

Redian新闻

>未名空间

>Java - 爪哇娇娃

求教：Facade Pattern vs Static Variable

求教：Facade Pattern vs Static Variable# Java - 爪哇娇娃

G*l2013-10-24 07:10

1 楼

请教在ACCESS query中, 如何count 每个有ID几个consecutive/continuous date for
each task?
JOB ID Date
TASK1 A 4/12/2009
TASK1 A 4/13/2009
TASK1 A 6/2/2009
TASK1 A 6/3/2009
TASK1 A 6/4/2009
TASK2 A 6/5/2009
TASK2 A 6/6/2009
TASK2 A 6/7/2009
TASK2 A 6/8/2009
TASK2 A 6/9/2009
TASK2

l*o2013-10-24 07:10

2 楼

I am maintaining a legacy SDK. The SDK will behave differently for different
platform. It's using a static variable and requires the static variable to
be created before any API call like the following:
Example for static variable (OLD CODE):
SDKContext.init();
VideoManager manager = new VideoManager();
public void VideoManager#search() {
SDKContext.search();
}
Components like VideoManager are all over the place. My gut feeling tells me
I should use Facade pattern instead, but can't be sure.
Example for Facade (MY PREFERRED WAY):
SDKContext context = new SDKContext();
VideoManager manager = new VideoManager(context);
public void VideoManager#search() {
context.search();
}
What's the pros and cons of facade pattern vs creating all API using a
static variable and invoke it implicitly? Any recommendation/suggestion is
welcomed.

g*g2013-10-24 07:10

3 楼

Depends on how heavy is SDKContext creation and whether it's thread safe to
share it. You may have different approach.

s*e2013-10-24 07:10

4 楼

Maybe I misunderstood you. But I do not think this is the case for the
facade. I do not think you are coding a facade even you call it so.
Maybe what you really need is the factory method or abstract factory.
Usually a static variable can be coupled with the abstract factory.