Backend - Implement ping

[haxwell]

So far, the 4 restriction levels are:

Directly having the attribute

Having the attribute and having it be cosigned

Having the attribute, having it be cosigned by a specific person

Pinger (person who is making the ping) is connected with the announcer

These restriction levels should be stored in the database. We also need an announcements table, which contains the announcement itself, and an announcement_details table, which contains information about the announcement’s restriction level.

When a ping is made, get the whole list of announcements. Then on backend, if the announcement applied to the user isn't already cached, then filter like so:

{code:java}public boolean doesUserHaveAttribute(Long phraseId, Long userId) {

return True if query returns a record else False }{code} Cache the announcement + the result of its filters being applied to user. If the announcement applied to the user is already cached, then return the results that already were calculated. Return results to frontend. Example of a cached record: Key: announcement ID + user ID + restriction level Values: True or False

• © Githubissues.
• Githubissues is a development platform for aggregating issues.