Re: Problem with securities in CVS version

> Looks great now, thanks for the quick turn-around.

NP

> I do have one comment for you.  It may mislead someone to fill in the
> OfxSecurityData::unitprice field of the security in
> OfxTransactionData::security_data_ptr, because the price might appear to
> be associated with the transaction, but it is definitely not.

Well, it's clearly part of the security.  Avoiding them getting confused is 
not worth having them store all the security data locally for future lookup 
IMHO.

> Also, do you have any near-term plans to support INVPOSLIST?  Some
> brokerages seem to only report usable pricing information in the
> INVPOSLIST aggregate (leaving out the DTASOF element from SECINFO in
> SECLIST).  Plus it would allow us to reconcile the user's investment
> statement.

I don't intend to work on it, but it would be fairly easy to do.

-- 
Benoit Grégoire, http://benoitg.coeus.ca/


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php