Dear all,
I have a question regarding the way ArticleCreate and
ArticleWriteAttachments are handled in kernel modules and generic interface
operations. I'm sure there must be some reasoning behind the way it works
and I'd be happy to understand it.
Almost everywhere were a new article with attachments can be created, the
preferred way to handle this is creating a new article and then writing the
attachments, although article create can handle attachments and would send
the article create event after the article is totally complete. This seems
to me a way of raising an event when the article is not yet complete and
using an "internal" function (not really internal but I would say that only
the Article object should have the need for writing and deleting
attachments from an article) from outside the object.
Could anyone explain to me why the preferred way is NOT passing the
attachments to ArticleCreate?
Kind regards,
juanma
