Okay...
In CVS now is a Supply-and-Demand example, which attempts to match
up buyers and seller.
./build.pl examples
Anyhow, this has shown me that we might need some more functionality
in the core engine.
While it does successfully match a buyer who's willing to pay what a
seller want, it does not optimize by linking the buyer to the cheapest
seller.
We *could* accomplish this already with a SellerCollection which sorts
by price, and each buyer just works against the head of the list, but
that's just somewhat unnatural.
Though, I'm at a loss for a better solution.
Anyone with experience with JESS or JRules have any clue how/if they
accomplish sorting and aggregation?
I know JRules does *something* with aggregation, where a Seller could
be aware not just that he has a Buyer, but how many Buyers match him
out there.
I'm just not certain.
Anyhow, I'm looking for discussion, and possibly use-cases, if you've
got them.
Anyone think they need sorting/aggregation of root fact objects?
-bob
_______________________________________________
drools-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/drools-interest
