O
onnodehaan
Guest
For me personally I can't understand why PSC won't fix these sorts of problems. Of not recognize the hurt it is doing to some ISV's. The answer states "It was determined that this is expected behavior for the third party software involved, and would require significant research to potentially find a replacement product which works better in a multi-threaded model.". That is very true of course. It is the expected behaviour for the third party software, but NOT for PSC end-users, customers, ISV's. OpenEdge is increasingly becoming a back-end languague in my opinion, processing data from website's and apps. XML is still very widely used and that will remain so for the forseeable future. So I would thing that if PSC wants OpenEdge to stay relevant it should not settle for "it was determined..."-like answers, but should take full responsibility in taking away bottlenecks like this. And if that's something that has a lower prio for now, fine... but in that case, they should at the the very minimum recognize the pain that these kind of problems cause us and make sure that it gets the attention it needs somehow.
Continue reading...
Continue reading...