Comments

7 comments

  • Bilal Al-Shahwany

    Hi Netanel, here are explanations for these URLs:

    https://sdk.split.io/api/splitChanges?since=1602230104343

    This is the polling thread to sync the Split changes from Split cloud to the SDK cache, SDK will use the polling thread if the streaming connection is disabled or error out. You can change the frequency of calling this URL by updating parameter "featuresRefreshRate"

    https://sdk.split.io/api/mySegments/null

    Same as above, this is the polling thread to sync the Segment changes from Split cloud to the SDK cache, You can change the frequency of calling this URL by updating parameter "segmentsRefreshRate"

    https://streaming.split.io/sse

    This is the streaming websocket connection that sync split cloud changes to SDK cache, either this or the polling threads has to be active so any changes in Split UI is synched to SDK.

    https://events.split.io/api/metrics/times

    https://events.split.io/api/metrics/counters

    These URLs are telemetry info posted to Split cloud, you can change the frequency of posting by updating parameter "metricsRefreshRate", set it to a high number to reduce these calls if needed.

     

    Thanks

    Bilal

    1
    Comment actions Permalink
  • Netanel Basal

    Thanks, Bilal. 

    As I understand it, it's for cases where I change one of the splits, and the user didn't refresh the page? It means that you'll update the SDK in real-time, and the changes will be reflected in the UI?

    0
    Comment actions Permalink
  • Bilal Al-Shahwany

    The changes will be reflected in the SDK cache, you can reflect the change in the UI by listening to SDK_UPDATE event - This event fires whenever a split or segment is changed. You can reload your app every time the event is fired.

    Thanks

    Bilal

    0
    Comment actions Permalink
  • Netanel Basal

    Thanks, Bilal, but it doesn't work.

    I've changed my config to:

    const NEVER = 100000000000;

    scheduler: {
      featuresRefreshRate: NEVER,
      segmentsRefreshRate: NEVER,
      metricsRefreshRate: NEVER,
    },

    and it stills sends a request each 60 sec. Do I have any way to debug it in production, and check why it doesn't work?

     

     

    0
    Comment actions Permalink
  • Bilal Al-Shahwany

    Hi Netanel, what is the request you are seeing? could you share the URL?

    Thanks

    Bilal

    0
    Comment actions Permalink
  • Bilal Al-Shahwany

    Hi Netanel, try enabling the SDK debug log which will show up in the browser console, the time you set might be too large.

    Thanks

    Bilal

    0
    Comment actions Permalink

Please sign in to leave a comment.