On 3/1/06, Kent Sibilev <[EMAIL PROTECTED]> wrote: > I've attached a new version of AWS patch. It 'partially' fixes 1889, > meaning that it allows embedding ActiveRecord objects inside of > AWS::Structs. > > So far this patch fixes: 2553, 3421, 2078, 2390, 2633, 2769, 3055, > 3576, 3321, 1889, 3567. >
Hi. Thanks Kent and others for stepping up to do this, I'm glad someone was able to cover this. Just to give you all an idea of what's up (not that you haven't managed to do just fine without me :) I've been putting off writing this email for far too long, and its way overdue. So overdue. I don't really have time to do any development on AWS (as you may have noticed). Scope change of my position at work means I have significantly less free spare time, so its hard for me to fit in stuff like AWS in my spare time, or into work time (as I was doing before). I most humbly apologize to anyone inconvenienced by my extended absence, it was not my intention to leave this unclarified for so long. As I will not have time to maintain this, I hereby want to cede any copyright I may have over all parts of AWS to the Rails project (or David Heinemeier Hansson if the Rails project is not a legal entity), just so there's no ambiguity should anyone wish to effect a license change or any such thing in the future. If someone wants to run with this, the codebase as it stands, while working, is fragile in its dependency on SOAP4R. The main reason for this is that it uses SOAP4R as a "SOAP message serialization/deserialization engine" and not much else, the reason for that being I needed more control of how messages were dispatched into method calls on controllers/services, as well as being able to have SOAP4R deserialize/serialize into the object types we expect. The result of this approach is that we need a bit more access to SOAP4R internals than I believe the author intended people to have, and hence its fragility. It may be worth for someone investigating if there are alternate approaches to my implementation for the newer releases of SOAP4R. In addition, it could benefit from a rewrite. I have no doubt it could be made much more compact, with less "meta" magic (other than that necessary for the current style of declaration and annotation) to make the flow easier to follow. I'll be adopting a seriously low profile from now onwards. Keep on having fun, folks :) Regards, Leon _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
