Bulk requests about intercom-php HOT 4 CLOSED

IMHO, I think these kind of things needs to be done in the background, if Intercom has a hiccup or there are some network issues reaching Intercom, your app might go down (I guess it depends on how you implement it).

What I'm doing is I put these in a queue and process them in the background.

Just my 2 cents :)

from intercom-php.

@everdaniel I don't disagree with that, because what I'm raising is not the workflow problem you have explained.

The issue is that it's a large overhead to initiate new requests when you're utilising a high latency connection to Intercom's API.

By doing bulk, it will allow for streaming behind a single request (albeit chunked) thus reducing the repeated handshaking requirement.

This problem is particularly compounded over SSL connections.

from intercom-php.

If you are having problems with load times, unless you are using the Intercom to persist your user data (unlikely?) I would recommend closing your connection to the client and then proceeding with the API call. To avoid causing multiple transactions chuck a lock into the session to tell subsequent connections to wait.

Regarding reducing latency, it would be nice to post the tags along with the user on creation.

from intercom-php.

We have no plans right now to add new bulk endpoints beyond what we currently offer: https://doc.intercom.io/api/#bulk-user-creation

Generally we recommend that Intercom actions are done async as suggested by @everdaniel

from intercom-php.