Comment

Comment by ta1243

The standard approach is be liberal in what you accept and be specific in what you emit.

You could

1) Filter the broken message

2) Drop the broken message

3) Ignore the broken attributes but pass them on

4) Break with the broken attributes

To me, only 4 (Arista) is the really unacceptable behaviour. 3 (Juniper) isn't desirable but it's not a devastating behaviour.

EDIT: Actually rereading it, Arista did 2 rather than 4. I think it just closed the connection as being invalid rather than completely crash. That's arguably acceptable, but not great for the users.

parent ta1243 1 year ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton