You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The create method takes both an address and an inboxId. When creating a client for the first time, an apiClient is initialized to call getOrCreateInboxId, and another is created during create. This double initialization contributes to the performance issue.
My initial thought was that create should only take an address, and we should handle fetching or creating the inboxId internally. However, we’re constrained by the need to pass the database path to create, and the database path is based on the inboxId. This means the inboxId must be known before calling create.
Lets think about how we might be able to improve this long term.
The text was updated successfully, but these errors were encountered:
The create method takes both an address and an inboxId. When creating a client for the first time, an apiClient is initialized to call getOrCreateInboxId, and another is created during create. This double initialization contributes to the performance issue.
My initial thought was that create should only take an address, and we should handle fetching or creating the inboxId internally. However, we’re constrained by the need to pass the database path to create, and the database path is based on the inboxId. This means the inboxId must be known before calling create.
Lets think about how we might be able to improve this long term.
The text was updated successfully, but these errors were encountered: