Notifications called more than once?

I receive new order notification more than once some times.
My hunch
is that this only happens when the notification component at
google is
unable to connect to our receiver, so it places it on some
kind of
queue. After some time it tries again when it is successful,
it sends
the first one again from the queue. Though it does not
affect my code,
but is this normal behaviour? I presume this could happen
with all
notifications. May be dangerous for our charge amount
notification as
it simply adds the amount paid whenever it receives a
notification. It
would be time consuming for us to check if the notification
data was
sent earlier. It is purposeless, probably the bandwidth and
processing
time can be saved.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "API Integration Basics" group.
To post to this group, send email to
google-checkout-api-integrationgooglegroups.com
To unsubscribe from this group, send email to
google-checkout-api-integration-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/google-checko
ut-api-integration?hl=en
-~----------~----~----~----~------~----~------~--~---

This is probably due to your server taking too long to
respond.  If we
do not receive a response from your notification handler
within the
time out period, Google Checkout automatically assumes the
sending
failed and re queues the message.  In order to prevent
duplicates, you
can check the order number or serial number of the
notifications
received.  I don't think that should take excessive
processing/
bandwidth?

-Peng

On Oct 2, 10:13 pm, epe <check...elevenplusexams.co.uk>
wrote:
> I receive new order notification more than once some
times. My hunch
> is that this only happens when the notification
component at google is
> unable to connect to our receiver, so it places it on
some kind of
> queue. After some time it tries again when it is
successful, it sends
> the first one again from the queue. Though it does not
affect my code,
> but is this normal behaviour? I presume this could
happen with all
> notifications. May be dangerous for our charge amount
notification as
> it simply adds the amount paid whenever it receives a
notification. It
> would be time consuming for us to check if the
notification data was
> sent earlier. It is purposeless, probably the bandwidth
and processing
> time can be saved.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "API Integration Basics" group.
To post to this group, send email to
google-checkout-api-integrationgooglegroups.com
To unsubscribe from this group, send email to
google-checkout-api-integration-unsubscribegooglegroups.com
For more options, visit this group at http://groups.google.com/group/google-checko
ut-api-integration?hl=en
-~----------~----~----~----~------~----~------~--~---