colinross / connection-compass Goto Github PK

Responsible for connecting to a SERVICE API, given CREDENTIALS, and retrieving a json/xml payload of contact data that is cached.

The results for my Denver, CO search were ordered:

Boulder, CO
Denver, CO
Golden, CO

It was strange that Denver the exact match was in the middle. I'm assuming that there is probably some logical explanation for this based on the search radius and algo that brings it up... but it probably means that something should be changed to address the irregularity.

I randomly selected a number of connections and clicked through to get more information/view their profile. About half of them pulled up my profile instead. In the brief period of testing I was able to do I didn't discover a pattern, or notice anything specific or similar across the "failures".

A redis-backed transparently cached NET::HTTP Client

There were a few connections I noticed I had, that were absent on some searches for their current city.

For instance a friend I know lives in Boston, and confirmed by viewing her profile to see her current city set as Boston, MA, did not show up in the list of connections when I used Boston, MA as the override city. This was duplicated with another connection of mine for an NYC search as well.

Again I didn't initially see any similarities between the two in the short test I was able to perform.

Tested across multiple users. Including both new and returning visitors, currently logged in and upon new session (logging out of Facebook and re logging in and reconnecting with the app.)