Answer:
See explaination
Explanation:
#include <iostream>
using namespace std;
int main()
{
double h, w;
int s, a, b;
cout<<"height in feet: ";
cin>>h;
cout<<"width in feet: " ;
cin>>w;
cout<<"tile size in inches:";
cin>>s;
int height = h*12;
if(height%s==0)
a = height/s;
else
a = height/s + 1;
int width = w*12;
if(width%s==0)
b = width/s;
else
b = width/s + 1;
cout<<"Number of tiles: "<<a*b;
}
Some of the disadvantages of using layered protocols are the redundancy and overall lower performance.
Reimplementing everything from remote and wired to connectionless and association situated application correspondence, with each ringer and shriek of BGP, MPLS, multicast steering and so on would be a gigantic endeavor and potentially unmanageable in this solid across the board convention. I could envision specialty utilize situations where most extreme execution is imperative most importantly where an exceptionally basic framework might be wanted.
