Design pattern to separate messages from actual process.
Posted
by Manish Gupta
on Stack Overflow
See other posts from Stack Overflow
or by Manish Gupta
Published on 2010-05-12T11:05:31Z
Indexed on
2010/05/12
11:14 UTC
Read the original article
Hit count: 226
design-patterns
|c#
I am having a C# application to sync data between PC and palm devices. There are codes written like below:
showMessage("synchronizing Table1");
Sync(destTable1,sourceTable1);
Sync(destTable2,sourceTable2);
showMessage("synchronizing Table2");
// more code
How do I separate the actual process of synchronizing from displaying message? Which design pattern to follow?
Thanks in advance...
© Stack Overflow or respective owner