One of our customers just migrated to an E4B, with our client-server CRM
product.
When the client sends a request that involves writing or updating a
server record, the record itself follows, sent and received separately
(but through the same persistent connection, and with built-in
safeguards against the records becoming stuck together and read as a
single record).
At any rate, this client seems to have developed strange issues,
immediately upon migrating to the E4B, anytime a write or update request
is processed. Supposedly, nothing has changed but the physical midrange box.
Has anybody ever heard of an E4B having this sort of problem?
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
