Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Why does mozilla Thunderbird Adressbook 'ldap implementation require special schema when you could use fields that are redily available in the basic schemes.

  • 1 отговор
  • 2 имат този проблем
  • 1 изглед
  • Последен отговор от Matt

more options

Hi i found it very disturbing that people who program mozilla's address book didn't think of looking at what basic core shema and additional basic ldap implementation had for ldap fields

for example a very basic install of slapd provides "homePostalAddress, postalAddress,registeredAddress,postalCode , street, l (locality) st (state), etc all fields/attributes that could be used to store home addresses , work addresses etc .

instead you just decided that instead of looking up those fields/attributes ( that are pretty standard) you would just lookup random "homebrew" attributes that no other application or software will use. not only at the expense of the technician who will need to fill those in but also duplicating efforts on top of efforts. compound this with the fact that pretty much all of you guys pull the same shit in every other address book application : ms exchange, android ab , iphone address book etc ... cant you guys get your dam ducks in row and use readily available info / structure ? or at least look at what others are doing and try to standardize this crap . its not that hard just takes a bit of dedication in doing your work properly.

Hi i found it very disturbing that people who program mozilla's address book didn't think of looking at what basic core shema and additional basic ldap implementation had for ldap fields for example a very basic install of slapd provides "homePostalAddress, postalAddress,registeredAddress,postalCode , street, l (locality) st (state), etc all fields/attributes that could be used to store home addresses , work addresses etc . instead you just decided that instead of looking up those fields/attributes ( that are pretty standard) you would just lookup random "homebrew" attributes that no other application or software will use. not only at the expense of the technician who will need to fill those in but also duplicating efforts on top of efforts. compound this with the fact that pretty much all of you guys pull the same shit in every other address book application : ms exchange, android ab , iphone address book etc ... cant you guys get your dam ducks in row and use readily available info / structure ? or at least look at what others are doing and try to standardize this crap . its not that hard just takes a bit of dedication in doing your work properly.

Всички отговори (1)

more options