On Jan 25, 2008, at 11:49, Jared Johnson wrote:
I'm wondering, is there some supported, "right" way to basically
clone a transaction so that I can modify aspects of it like the
message body and/or subject for one list of recipients while leaving
it intact in the original transaction object for the recipients for
which the message is passing through unmodified?
No - but it's definitely something we want.
I think the stumbling block has been figuring out the API for this.
We need a way to say "do it" (that should be pretty easy), "how to
access the extra information" (also pretty easy) and "how to make it
work for plugins that don't care" (maybe harder). We also need to be
able to "bounce" a transaction.
The "don't make the default harder than it currently is" bit is
important.
One way to approach it could be to leave the current transaction
object intact but add a method to say/query "do the recipients
individually" and then have a method to access the individual ones.
That way we can move plugins that need the extra information to use it
and the ones that don't care to, uh, not.
Maybe a method could do "give me all the recipient-transactions" which
will just default to the current transaction data.
Of course there are a bunch of edge cases -- what do you do when you
can/have queue(d) one message but the second one failed?
Anyway - it's great that you are starting on this; some real world use
cases will make it easier to guide the API.
- ask
--
http://develooper.com/ - http://askask.com/
