Skip to content

Questioning the value of the ability to change SFrame transform on the fly #298

Description

@alvestrand

With SFrame transform, we have a very limited set of possible transforms. The only part in which they can differ is in their key setting and their "type" configuration. Key setting is handled by AddKey on the receive side, so the only possible use case for changing a receiver transform is to fail receiving packets that were marked with old keys - this can also be handled with RemoveKey.

I fail to concieve of an use case where replacing or removing the recieve SFrame transform will be useful.
The only case where I can see changing the send Sframe transform would be useful is changing from type "per-packet" to "per-frame" or vice versa.

Is that use case worth the complexity of permitting replacing of the SFrame transform?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions