|
From: Pelle B. <pe...@ve...> - 2004-05-14 14:18:41
|
Deneb, I'm replying to the mailing list so we can document the requirements publically. The requirements as far as I see it is to: - Record all transactions for various accounts across asset types - Provide balance information and more Lets take an example flow of transactions here: Payor Payee Asset Amount Bob Alice bux 100 Bob Carol shoes 1000 Alice Carol bux 50 Carol Alice shoes 5 We assume that Bob had an initial balance of 200 bux and 1000 shoes. Alice and Carol had zero initial balance of either asset. Now the bux asset controller maintains a ledger of transactions within it's own asset. So it has the following of the above transactions: Bob Alice bux 100 Alice Carol bux 50 So bux has the following balances afterwards: Bob: 100 Alice: 50 Carol : 50 The shoe asset controller similarly maintains a ledger of it's own transactions: Bob Carol shoes 1000 Carol Alice shoes 5 Shoe maintains the following balances afterwards: Bob: 0 Alice: 5 Carol : 9995 Bob could check his balances on each of the asset controllers there, but it would make more sense if he had a portfolio manager locally or on a server that he trusted to do the accounting for him. This is where the Portfolio Manager comes in. The Portfolio Manager listens to all of Bob's transactions regardless of asset and stores them in it's own ledger. So of the transactions above the Portfolio stores the following in the ledger: Bob Alice bux 100 Bob Carol shoes 1000 With this Bob can immediately see his balances in all of his assets as being: bux: 100 shoes: 0 The portfolio manager is not only important to end users, but also in mutual fund style applications, where all the funds holdings could be held on a public server. The share holders of the fund could go in and view in real time the holdings of the fund. Now, my original plan was to have a separate portfolio manager. However I just realized that with the recent changes to the LedgerController. There is no real need for it. The current Auditor will actually do the whole thing without changes. What we may need are some changes to the reports generated afterwards. I will have to have a look. So it seems like we dont actually need a separate PortfolioManager class after all. Which means we can go straight to the DistributionController. -P On Thursday 13 May 2004 23:32, you wrote: > Hi > > Potfolio manager > I was searching this class .. it doesnt seem to be > there yet > > Is portfolio like the place for all assets, so do we > have to create a db where all the assets would be > stored > > for micro payments > what assets would we have > like its diffcult for me to understand due to lack of > finance knowlesge > > can u explain me the proto-type so that i can > understand better like > -- what all are we trying to exchange > -- is it a pre-paid kinda micro payment or a normal > one > > > can u guide me about portfolio manager [which package > and responsibility ] > > regards > deneb > > -- http://talk.org + Live and direct from Panama http://neuclear.org + Clear it both ways with NeuClear |