|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
Exchange operation connectivity requirements
Trying to gather functionality requirements for a customer-operated internal
exchange - and would like to solicit feedback on things that I am missing -
because frankly the list seems rather small right now :-)
From experience on the sender side (e.g. connect to a clearinghouse) the basics
are
- set time of day for connection
- limit number of bytes (or possibly file transfers)
- limit connect time or least make sure we have actually disconnected when done
What about from the clearinghouse side? In order to prevent connectivity at
"unauthorized" times do we need to:
- deny connections until agreed upon times? - capability to override this
option?
- enforce limit on number of bytes transmitted or is it standard to allow and
simply report overage?
- detect connections with inactivity
- what am I missing??
Any Feedback is extremely welcome!!!!!
|
|
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
