SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
SI - Site Forums : Silicon Investor - New feature discussion -- Ignore unavailable to you. Want to Upgrade?


To: The Ox who wrote (5897)4/11/2017 9:18:43 PM
From: SI Dmitry (code monkey)5 Recommendations

Recommended By
Bob
Gottfried
Stock Puppy
Terry Maloney
The Ox

  Read Replies (3) | Respond to of 7360
 
Dear Ox,

I've thought about this, but concerns about performance have prevented me. at least with the way we are doing things right now. When fetching the page for viewing a single post, the web server makes a second trip to the database server on our internal network to fetch the recommendations. The list of people who made the recs are served as part of the original page response served to you, and unhidden when you mouse over them using simple CSS. For a long list of posts, the additional server queries and responses to get the recs for each post would become expensive in terms of latency and network traffic.

What sites like Facebook do is intercept the mouse hover event and query their server during the time your mouse is over the link using ajax (asynchronous javascript and XML). This is why there is always a delay before the information is displayed. But the data isn't queried until you express your desire to see it in terms of a mouse hover.

For now, I'm afraid you'll have to click on the link to see the individual recommendation details when viewing a group of posts. I perhaps might like to optimize the database code to do it all in a single trip in the future. But with all the data grabbed when a long list of posts is displayed, this is already one of our most expensive operations, in compute resource terms. I always have to keep these things in mind.

Regards.

@Dima