---
# System prepended metadata

title: Solid Notification through Headers

---

# Solid Notification through Headers

SC (as understood by RG): Suppose an authenticated client access a topic resource either via a HEAD/GET or a POST; Is exposing websockets cURL in the header any different from going through subscription process from a security point of view.

RG: From what I understand, such a cURL will be a standardized channel specific to a topic, i.e. the client cannot add multiple topics or add features. This is undeirable! While this way would be more performant for a subscribing to a single topic, it will be scale poorly. 

As the number of topics in a websocket channel increases, using the subscription flow to get a cURL becomes more efficient! The former (SC proposal) will require client to manage each topic separately. However, this way a single websocket can handle all the topics on a pod/server. 

Therefore, I favour exposing Subscription Service on the header (same as the discovery resource) and let the client subscribe to that with all the topics/features it pleases. 