| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2987.1 | | METSYS::THOMPSON | | Tue Jan 28 1997 17:33 | 8 |
|
I think the code has been back and forth on this a few times.
In the past we have had caee-sensitive and case-insensitive. Whatever
way we set it we upset somebody. So we now have it as the X.400 Spec says -
case sensitive.
Mark
|
| 2987.2 | X.402 says NOT case-sensitive | ZUR01::ASHG | Grahame Ash @RLE | Thu Jan 30 1997 13:12 | 13 |
| > way we set it we upset somebody. So we now have it as the X.400 Spec says -
> case sensitive.
Yes, I'm sure you will! But I'm intrigued by your statement that X.400 says
case sensitivity is the way - where is this? In X.435?
From X.402, which defines O/R Addresses, Section 18.4 defines the rules for
working out if they are equivalent. This includes:
"Where the value of a Standard Attribute may contain letters, the cases of
those letter [sic] shall be considered insignificant."
grahame
|
| 2987.3 | Should not messages be written to DECEDI$ERROR: | RULLE::KLASSON | Sven-Olof Klasson @GOO | Thu Jan 30 1997 15:16 | 19 |
| Re: .2
Thanks for the pointer. I did try to find this in the blue book myself, but
that book is no easy reading....
Indeed the blue book says case should be insignificant!
Another aspect of this problem:
When PEDI fails to match O/R-names on an incomming message it will just
write a message in the errorlog, and then trow away the message.
I belive the X400 gateway saves the message as .CONTENTS and .ENVELOPE files
in DECEDI$ERROR.
I did expect PEDI to do the same. That would have give the customer a chance
to save the data. Since the MTA has allready sent back delivery notification
that transmission might be gone from the trading partners system.
Sven-Olof
|
| 2987.4 | | METSYS::THOMPSON | | Thu Jan 30 1997 18:41 | 8 |
|
I doubt that we checked the blue book but we probably did check the
the MRX programming guide.
There are implementations out there that can't change and so we had
had to be realistic.
M
|
| 2987.5 | XAPI is in-memory, not on-disc | ZUR01::ASHG | Grahame Ash @RLE | Fri Jan 31 1997 11:28 | 11 |
| Re .3 - PEDI "throws away" bad messages.
Yes, I think this is a symptom of the XAPI - the interface to the MTA. Unlike
in MRIF (as used by the X.400 Gateway) there is no concept of the message being
written to disc - it's held in memory by the MTA until the gateway tells the
MTA it's finished with it.
I imagine it would be quite a lot of work to write code which wrote the
message to disc.
grahame
|
| 2987.6 | SUGGESTION/WISH | OSL09::EVEN | Lars Even Christiansen @NWO, Oslo, DTN 872 8456 | Tue Mar 18 1997 10:43 | 16 |
| Hi
When taking the choice of case in-/sensitivity would upset somebody, it
would seem like a good idea to let the users make that choice, wouldn't
it?
E.g. an environment variable or a logical name on the machine on which
the PEDI gateway runs could be checked against in the code, before
matching O/R address with the connection ids.
I'd guess that would be a simple way of providing such a feature?
Of course it would be best if this was defined per connection id.
Regards,
LarsEven
|
| 2987.7 | | METSYS::THOMPSON | | Wed Apr 02 1997 15:44 | 10 |
| Hi,
We've just had a discussion on this. We're thinking about allowing
an incoming case-insensitive match - though keeping the case sensitive
outgoing name.
We will review this with the MTA folks first though - so no commitment
yet.
M
|