refs #463 and #464 were failing due to pilot error -- #463 was calling waitForData, which did exactly as it was designed -- waited (possibly indefinitely) until new data came in. None was being provided by the test, so it blocked. In #464, getNewData returns new data only if there is some -- on the second call to getNewData if no new data has been added to the reop in the interim, it will block (and should block) until data appears.
refs #463 and #464 were failing due to pilot error --
#463 was calling waitForData, which did exactly as it was
designed -- waited (possibly indefinitely) until new data
came in. None was being provided by the test, so it blocked.
In #464, getNewData returns new data only if there is some --
on the second call to getNewData if no new data has been added
to the reop in the interim, it will block (and should block)
until data appears.

There *is* a real problem on line 151, where a call to getNewData
when there should be new data does block.

cawka/ndnx,ebollens/ccnmp,svartika/ccnx,ebollens/ccnmp,svartika/ccnx,svartika/ccnx,ebollens/ccnmp,cawka/ndnx,cawka/ndnx,ebollens/ccnmp,cawka/ndnx,svartika/ccnx,svartika/ccnx,svartika/ccnx,cawka/ndnx,svartika/ccnx