![]() |
|
ECGridOS Developer Development related posts. |
![]() |
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
![]()
I sent a test file to myself which contained two different interchanges. The API for parcel_in_box specifies that I'll be receiving back a collection of InterchangeIDInfo objects. When I perform this request I actually got back two parcels, each with one InterchangeIDInfo object. Will ECGridOS be separating all inbound data as such and should I always only expect one InterchangeIDInfo in the parcel_in_box response?
|
#2
|
||||
|
||||
![]()
First, congratulations on successfully sending and receiving you first interchanges through ECGridOS!
The collection of InterchangeIDInfo objects is to accommodate systems that send us more than one interchange per mailbag/parcel. A number of the VANs and a few customers do this. We recommend only sending on interchange per mailbag/parcel, but it is not a requirement. We will always send one interchange per parcel to your InBox. The class object is set up to generically handle all InBox and OutBox possibilities, which is why it is set up as a collection for InterchangeIDInfo objects. -=tg=- |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Parcel Listing | MarcNelson | ECGridOS Developer | 1 | 09-13-2010 03:30 PM |
Parcel Download Date | MarcNelson | ECGridOS Developer | 1 | 06-03-2010 10:35 PM |
Codes & Tables | Todd Gould | ECGridOS Developer | 2 | 03-18-2010 04:56 PM |