...
Another option would be: use the (beta) built-in payload validation facilities of Crossbar.io. Ah, wait, that is using JSON schemas to define valid payloads .. wouldn't help much in your case .. you need to find script tags. So my recommedation: implement a "com.myapp.send_message" procedure with payload checking and publish therein.
...
Another option would be: use the (beta) built-in payload validation facilities of Crossbar.io. Ah, wait, that is using JSON schemas to define valid payloads .. wouldn't help much in your case .. you need to find script tags. So my recommedation: implement a "com.myapp.send_message" procedure with payload checking and publish therein.
--
You received this message because you are subscribed to the Google Groups "Crossbar" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crossbario+...@googlegroups.com.
To post to this group, send email to cross...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/crossbario/e607e62a-407a-4300-9a45-6ceef114bb37%40googlegroups.com.
Currently, your best bet is a component which subscribes to the topics which clients need to receive history for. This would then offer a RPC which components can call to get the required history.
There are no interceptors. To understand your use case better: What would be the difference between interceptor components which get called by the router versus an architecture where: all clients call a RPC 1 which filters out the special cases, calls a RPC 2 with the actual procedure for the non-special case and then returns the result? (Except for one round-trip.)
- I see that for the first part of my use case, there is a feature request: https://github.com/wamp-proto/wamp-proto/issues/69 , although I'd prefer to manage that in my own "interceptor" component.
- I posted a related question to SO: http://stackoverflow.com/questions/32726514/how-to-provide-both-initial-data-and-subsequent-events-via-wamp-websockets?noredirect=1#comment54184222_32726514Another option would be: use the (beta) built-in payload validation facilities of Crossbar.io. Ah, wait, that is using JSON schemas to define valid payloads .. wouldn't help much in your case .. you need to find script tags. So my recommedation: implement a "com.myapp.send_message" procedure with payload checking and publish therein.
Thanks for this.
On the other hand, I was actually looking for some way for a component to intercept published messages. I feel it'd allow for quicker development in my case.
Use case: I need to do some caching of some messages in order to repeat them for recently connected sessions. An interceptor would work. Later on I'll need to respond to some RPC calls with some special responses for some users (to avoid concurrent access to some methods). I'd like to offload that burden off the main process, and put it on the router, but I'll have to "proxy" all RPC calls within my component.
Is there such a thing as an interceptor?
Best regards!
--
You received this message because you are subscribed to a topic in the Google Groups "Crossbar" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/crossbario/LbfbxnSd5YA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to crossbario+...@googlegroups.com.
To post to this group, send email to cross...@googlegroups.com.
To unsubscribe from this group and all its topics, send an email to crossbario+unsubscribe@googlegroups.com.
To post to this group, send email to cross...@googlegroups.com.