Software architecture is considered as the high-level decompositions of software systems into components and connectors. Connectors herein represent the component interactions and may be as simple as basic communication links without any functionalities or complex mediators that enforce some quality requirements on the component interactions. In this paper, the existing 124 different architectural languages (ALs) are analysed to understand which type(s) of connectors they support. The connectors considered in this study are procedure call, event, data access, linkage, stream, arbitrator, adaptor, and distributor. The analysis of the ALs for those connector types lead to many interesting results some of which are as follows: (i) the link connector is supported by almost all the ALs, and half of those ALs further support the specifications of high-level connectors (i.e., interaction protocols) for the linked components, (ii) many ALs define the high-level connectors in terms of the formal specification languages and pi-calculus is the their top choice, (iii) most of the ALs consider the procedure call and event connectors basically for method invocation and data transmission respectively, (iv) the data access connectors are mostly used as a simple data flow mechanism, and complex mechanisms (e.g., data translation) are ignored, (v) the stream connectors are supported indirectly via the formal methods, (vi) the arbitrator connectors are mostly considered for dealing with the concurrency issues, and (vii) the distributor connectors are shown the least interest by ALs.