Opened 4 years ago

Last modified 4 years ago

#9949 new enhancement

have each fp client register at multiple custom facilitators

Reported by: infinity0 Owned by: dcf
Priority: Low Milestone:
Component: Archived/Flashproxy Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: #10711 Points:
Reviewer: Sponsor:

Description

This is related to #9942, but would be quite a bit harder to do, since we would probably also want a way for clients to cancel registrations once they've been served by a single proxy. Otherwise, the facilitators which didn't serve the client with a proxy, don't know that the client has already been served, potentially wasting resources.

Child Tickets

Change History (3)

comment:1 Changed 4 years ago by infinity0

We could also set an expiry time on client registrations. But that doesn't fully solve the problem, since there is still a period in which a facilitator might serve a proxy to a client that was already served by a different facilitator.

comment:2 Changed 4 years ago by dcf

Something I've talked over with ln5 (Linus Nordberg) is rather than having the client (knowingly) register at multiple facilitators, is to multiplex and distribute such registrations on the facilitator side; for example, further decouple facilitator-email-poller, and have it send some registrations to one facilitator and some registrations to another.

The main motivation for running multiple facilitators, as I understand it, is privacy of flash proxy operators. For example, a privacy-oriented web site wants to install the proxy badge, but doesn't want their visitors making requests to a third-party server. They can run their own facilitator, and configure their badge to make requests to it only. But then the question is of course, how does this new facilitator learn about any clients, when all existing clients are already configured to register with someone else.

Last edited 4 years ago by dcf (previous) (diff)

comment:3 Changed 4 years ago by infinity0

Parent ID: #10711
Note: See TracTickets for help on using tickets.