On 2012-07-13, at 1:41 PM, Farrukh Ijaz wrote: > > On 2012-07-13, at 11:11 PM, Chuck Hill <[email protected]> wrote: > >>> Is rewriting EOF and webobjects even a possibility? If yes, what about an >>> outline of what is required to undertake this magnitude of project. >> >> >> Yes, it is possible. It was written once, it can be written again. I don't >> know if it is practical though. I doubt that any or even all of us have the >> resources to fund that. Apple has a LOT of man years in WO. > > Rewriting EOF + new Bugs + Lots of Man Hours = Existing EOF + AOP Patched > Code + Few Man Hours
Don't forget that a lot of of the reason to replace WO was not to fix bugs but to address the perception that it is a dead technology. Using AOP to patch WO won't address that concern. > The only issue I would say which is an issue is maintenance of the patched > code. Since aspects reside outside and integrate at runtime, it will be > difficult for someone to trace where the bug is lying (in EOF or in the > patched code) unless it's well documented. Yes, that will be a problem. > The choice is in the hands of community but I think we should give AOP a try > before we start rewriting the whole EOF or go for alternatives, it's much > faster to test. After all, I will do what Romans do in Rome :) Drive crazy? :-P -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/gvc/practical_webobjects _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
