Dear Kenton Thanks for your answer and sorry for not being able to communicate the problem properly. I'll try to hand-code the protocol but I was trying to update the technology and make it more maintainable in both server and client side.
Again thanks for your time and effort. Abbas. On Sat, Sep 10, 2016 at 2:56 AM, Kenton Varda <[email protected]> wrote: > Hi Abbas, > > I just wanted to say, I read your message... but I don't think I really > understand the question, so I'm not sure how to answer. :/ > > I would note that when you're working with such constrained packet sizes, > it may become worthwhile to hand-code your data format rather than use a > serialization framework like Cap'n Proto or Protobuf, as you'll want to > optimize out every byte you can. > > -Kenton > > On Wed, Sep 7, 2016 at 1:32 AM, <[email protected]> wrote: > >> Hi everyone >> >> I'm noob hear, so Please bear with me to explain my problem. >> >> My problem is I want to send files to embedded systems(Linux based EFT >> POS) that use HDLC dialup infrastructure for its communication. >> In our company we have too many terminals that connect to our >> infrastructure using HDLC dialup lines. >> Let me explain a little about how things works in this infrastructure. >> >> - Terminals connect to something called Concentrator(for example >> Verifone's Intellinac) to convert HDLC data frames to TCP Packets. Each >> packet is sent to server. >> - Each packet contains a special header called(TPDU) that consist of >> 5 bytes: 1 protocol identifier, 2 bytes refer to source address and 2 >> bytes >> to destination address. >> - Every time a terminal sends a packet Concentrator change it source >> address to it's next first free address(something like NAT) >> - Two consequent packets from a terminal may have different source >> address (there is no stream. it is more like UDP) >> - AFAIK the packet's can not be more that 1024 bytes for >> compatibility issues >> - Each packet must have an ACK packet >> >> I'm trying to design a cap'n proto scheme to make me able to do following: >> >> - I can identify the sender by some sort of ID >> - I can make sure the packets are at most 1024 bytes >> - I can find out how many packets form a file >> - I can find out what is the sequence of current packet >> - I can ACK each packet >> >> >> First thanks for being with me until here, I'm seeking your opinion over >> this and trying get suggestion on how can I handle it. >> >> Thank you in advance for your help >> >> Warm regards, >> Abbas. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Cap'n Proto" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> Visit this group at https://groups.google.com/group/capnproto. >> > > -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/capnproto.
