maglomanic
Junior Member
Ok my last one on this.
I have stated it before. Protocol is when to expect what. Do you really think Erieye won't give Pakistan native api that will sit on top of their hardware and allow them to not only know that "what and when" ?? dealing with collisions again is nothing new. depends on how protocol deals with it. Do they send a "resend" bit? if they do then the other side just need to look for that bit. Very standard stuff.
Think about the network device on the Mainframe that was created way before the network card on Xeon server. Think about the network latency synchronization issues. And no we implemented our own driver or emulator if you wish to call it that, that would understand the TC/IP which was being used on Xeon.
Designing ports of a device is not application level. Thats your physical layer which involves Digital signal processing. I have said that it is very unlikely that China cannot implement that protocol. If you know What to send and when to send,then "how to send" becomes quite immaterial.tphuang said:yes, again, this is all application level
that's the point I'm making if you use another protocol, it is very unlikely that it can connect to link 16. For example, if you use UDP, it doen't even require a connection with the other side.
that's not what the protocol is about. The protocol is about how you send and receive the data. How you guarantee delivery and what to do when you get too many collisions. Encryption is a very small part of it.
I have stated it before. Protocol is when to expect what. Do you really think Erieye won't give Pakistan native api that will sit on top of their hardware and allow them to not only know that "what and when" ?? dealing with collisions again is nothing new. depends on how protocol deals with it. Do they send a "resend" bit? if they do then the other side just need to look for that bit. Very standard stuff.
they can't, it's not about native API. Even with time changes, the protocol of transport/network is still the same between a mainframe and a xeon server. Or at least it implemented the protocol of that old mainframe. I'm telling you right now that China is using one transport/network protocol and Link-16 is a different one.
Think about the network device on the Mainframe that was created way before the network card on Xeon server. Think about the network latency synchronization issues. And no we implemented our own driver or emulator if you wish to call it that, that would understand the TC/IP which was being used on Xeon.