Thanks Gareth, and I'm glad to hear that you've done this task with such
success! that's one more argument indicating this is the right thing to do,
taking into account the requirements of my apps.
Best regards.
On Thu, Jan 6, 2011 at 2:46 AM, Gareth McCumskey wrote:
> That would have been my w
That would have been my way-to-do-it-right-but-time-consuming idea for you.
We in fact have done that ourselves we have a full API system to assist
communications between multiple applications (some with code we have no
access to) and it works beautifully. Good luck with implementing your
solution
First of all, thanks a lot for your feedback on this matter Gareth. it's
really very helpful.
The notification via web services as you've described is almost exactly what
I have in mind for my actual app. But with only one difference. I want to
create a "middle" app between the rest of application
Perhaps your best bet for this kind of system is to create some kind of web
services API on the other applications (REST, SOAP, whatever floats your
boat). Then when you create an entity and need to notify these other apps
you can do so directly by targetting their web services API and notifying
th
I mean a notification system for other apps that may have to react to the
event descripted on the notification. If this notification never arrives,
the other apps couldn't be react as they should on that event. Of course I
can mark the step as failed and retry later. Of course I'm looking for an
ed
I still question whether the notification event, by whatever mechanic you
decide, is really that critical for success. Do you really need to base the
entire success of the transaction in part on the success of a courtesy
message? Is the message itself really that critical to the success of the
tran
Thanks for your answer Gareth.
I used an email send as a step just for simplicity. It's very true that
email sending is very unreliable. I was really thinking in every case. Maybe
register a message in a message service to notify other applications
involved of the event ocurred? the only thing tha
Email is not reliable. Its as simple as that. The reason I say this however
is that when you rely on systems outside of your control, such as mail
servers because remember, the recipients mail server also needs to be fully
functional, you need to bear in mind that reliability is very likely.
All y
Hi all,
I know is not a Symfony specific question but I was wondering how do you
guys manage a situation like the following:
. Create an entity and save it to the database
. Save the log to a file or whatever resource the system has
. Send an email to notify people involved with the entity that t
