Design and Architecture

Rajeshjoseph wrote:

In a scenario where a customer updates a field - say name - immediately two or more times, ....Any recommendations on the best way to implement such a functionality?

Rajeshjoseph wrote:

I was trying to work out a solution for a scenario where a customer updates his "First Name" twice in the interval of say 5 minutes - in this scenario - with the planned architecture - the second update will be displayed on the web as soon as it is done,

Eddy Vluggen wrote:

your question is too vague

sseth21k wrote:

I have a solution to the problem. But I would like to know other approaches to solve the issue.

class AccountInterface
{
public :
	virtual void CheckAccount() = 0;
};


class Accountant 
{
private:
	AccountInterface * accountDept;
public:
	Accountant():accountDept(NULL){}
	void SetCompanyAccDept(AccountInterface *accDept){accountDept = accDept;}

	void AuditCompany()
	{
		if (accountDept)
			accountDept->CheckAccount();
		else
			printf("Compnay info not set");
	}
};

class company : private AccountInterface
{
private:
	virtual void CheckAccount()
	{
		printf("Only Granted Accountant should have access to this");
	}
public:
	void SetAccuntant(Accountant *accountant)
	{
		//Based on some logic grant access
		accountant->SetCompanyAccDept(this);
	}
};

int main (int argc, char *argv[])
{
	company c1;
	Accountant ac1;
	c1.SetAccuntant(&ac1);
	ac1.AuditCompany();
	
}

SSETH wrote:

Could you please post here your approach(Design) in C++..

sseth21k wrote:

1. The third person should not be able to see the other details of the class!

sseth21k wrote:

the component should be accessible to only that particular third person!