▁services ▁over ▁that ▁technology . ▁Hence ▁the ▁same ▁service ▁can ▁be ▁implemented ▁over ▁ground - based ▁network ▁techn ologies ▁and ▁middle ware , ▁or ▁it ▁could ▁even ▁be ▁carried ▁across ▁the ▁space ▁link ▁itself . ▁The ▁services ▁themselves ▁provide ▁the ▁‘ pl ug - and - play ’ ▁interface ▁for ▁applications , ▁allowing ▁them ▁to ▁be ▁integrated ▁and ▁deployed ▁wherever ▁is ▁appropriate ▁for ▁the ▁mission . ▁ ▁There ▁are ▁no ▁performance ▁overhead s ▁as ▁the ▁M AL ▁layer ▁is ▁concept ual ▁and ▁can ▁be ▁optimized ▁out ▁using ▁code ▁gener ators . ▁ ▁Dis adv antages ▁ ▁The ▁M AL ▁will ▁not ▁support ▁features ▁of ▁the ▁underlying ▁protocol ▁beyond ▁the ▁" le ast ▁common ▁denomin ator " ▁defined ▁in ▁the ▁M AL . ▁ ▁Mess aging ▁features ▁( e . g . ▁thread ing ▁model , ▁Q o S , ▁etc .) ▁are ▁limited ▁to ▁a ▁simpler ▁subset ▁that ▁represent ▁the ▁intersection ▁of ▁all ▁of ▁the ▁underlying ▁middle ware ▁options . ▁However , ▁feature ▁of ▁an ▁underlying ▁protocol ▁may ▁be ▁selected ▁through ▁configuration . ▁ ▁An ▁adapter ▁layer ▁between ▁M AL ▁and ▁the ▁underlying ▁protocol , ▁plus ▁specific ations ▁for ▁language ▁bind ings , ▁are ▁still ▁required . ▁ ▁Im plement ations ▁must ▁ad here ▁to ▁these ▁specific ations ▁for ▁inter oper ability . ▁ ▁Thus ▁M AL ▁takes ▁on ▁the ▁characteristics ▁of ▁becoming ▁new ▁middle ware ▁standard ▁in ▁itself . ▁ ▁The ▁M AL ▁ad ap ters ▁and ▁the ▁M AL ▁language ▁binding ▁specific ations ▁must ▁be ▁maintained ▁as ▁the ▁underlying ▁middle ware