Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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.

Pastimes : Silicon Investor ThinkTank -- Ignore unavailable to you. Want to Upgrade?

To: wlcnyc who wrote (1333)	6/6/2000 9:59:00 PM
From: mr.mark	Read Replies (1) \| Respond to of 3372

hi bill in referring to the fact that "SI has a "Terms of Use" code that limits a poster to 20 messages within six hours", you went on to add, "Imagine the reduction in number of posts if that rule were applied (and enforced) on RB or Y!". yes, and imagine if the rule was applied (and enforced) on si :) mark

To: wlcnyc who wrote (1333)	6/7/2000 10:57:00 AM
From: Green Receipt	Respond to of 3372

an easy way SI could solve this problem would be to emply user semaphores. When a user presses 'submit' and the transaction hits the SI server, the SI server immediately (first thing) creates a 'lock' for the particular user. When the transaction finishes, the lock is 'cleared'. Any 'duplicate transactions (generating the same lock)' would be blocked while the lock is set. This lock could be as simple as a combination of the message id you are replying to, a checksum of the text you are submitting, and the submitter's userid. Given the scenario where someone presses submit twice in succession for the same message, this solution would effectively block the duplicate messages from being processed/posted. Just my 2 cents worth. David