For Twitter related services we currently have various "inbound-channel-adapters" and "outbound-channel-adapters" available.
For example we have the "Search Inbound Message Channel Adapter", which polls Twitter periodically for search results. The execution of the Spring Integration "flow" is triggered by the poller. However, what if the search shall be triggered from e.g. a generic Gateway - Meaning the end-user/business-application is intending to execute the search which will then cause Spring Integration to make an outbound search request to Twitter and the search results will be returned to the caller?
I believe there might be a use-case for an Outbound Twitter Gateway.