Implementing these in a subclass requires you to ensure that the objects you are working on belong to that subclass. Categories allow you to apply your methods to objects returned by frameworks without casting/modifying them.
ALTERNATE/MIRROR LOCATION with proper HTML
on
Dissecting the Roomba
·
· Score: 2, Informative
Reminder: If you're considering this, remember that PowerFile is majority-owned by Escient, the company responsible for appropriating the CDDB's content under an aggressively restrictive and monopolistic license.
The NeXT development tools (from which OS X's Project Builder is descended) shipped with multiplatform compilers and libraries, and cross-compiling for 68k, x86, Sparc, and HP PA-RISC (and in theory PPC and Alpha, though never publicly) was a matter of selecting the appropriate checkboxes for the project. (Or adding "-arch i386 -arch m68k -arch hppa -arch sparc" to your (g)cc command line.)
Remember, GCC is built for cross-compilation, and, in this case, Apple controls the OS packaging and is able to supply consistent cross-platform libraries.
Also, FYI, the application bundle format is designed to support multiple hardware architectures as well...
As an intriguing point for this thread, Don Box brought an iBook running OS X to this past summer's TechEd conference to give his presentation on XML/SOAP interoperability... (forgot the VGA adapter cable, though...)
Mulberry (from Cyrusoft: http://www.cyrusoft.com) has Win, Mac, Solaris, Linux clients. It's commercial but worth it.
Has preset identities, which can group an outbound mail "account" and a variety of headers, sigs, and signing/encryption keys. Can configure outbound mail in response to mail in a specific mail "folder" to default to a specific one of these identities.
Automated filter rules are in alpha and need some work, but are almost there.
S/MIME support is planned but not there.
PGP support is in there.
Supports IMAP (full online, offline, or disconnected: offline filing, mailbox creation, etc. work properly), POP and local mailboxes.
Both client and server roles are possible, but some uses require somewhat complex configuration.
Please note that Kerberos _authentication_ is unchanged and *completely* interoperable. The only issue is that any vended service which wishes to use the Microsoft authorization data (which is likely to include many or most Windows-hosted services) must receive and understand the PAC.
Samba can (theoretically) operate as a W2K fileserver, using Kerberos, with no issues. It needs to make authorization decisions based on group membership information derived from some other mechanism, however, rather than basing them on group IDs embedded in the PAC field of the Kerberos ticket.
The reverse is manageable as well -- since the *nix box has no conflicting use for the PAC, it is saved by the (Unix) client which thus presents an appropriate ticket to the W2K-based file server when issued the ticket by a W2K KDC; if the ticket is issued by a Unix KDC, a Windows KDC must exist which trusts the Kerberos realm from which the Unix ticket is issued. However, given that you're connecting to a Windows service, the burden of that is not as high as it might otherwise seem.
The major issue with Microsoft's Kerberos implementation is actually:
1. A Unix KDC operating *without* an additional W2K KDC cannot vend tickets to Windows-hosted services which require the PAC to authorize users. Please note, however, that if a W2K-hosted KDC exists, it can trust the non-W2K KDC's tickets for cross-realm authentication, and use them to automatically grant a W2K ticket for access to the W2K-hosted service. Since most services requiring that authorization data would be Windows-hosted anyway, the major issue becomes:
2. The ability to manage a Unix-hosted service using the Microsoft management tools (i.e., establishing the W2K equivalent of a primary domain controller) cannot be made to exist without disclosure of the PAC format. This blows some of the supposed ease-of-administration benefits of W2K away unless you're running W2K servers.
These are frustrating, and the second might constitute an anti-competitive action, but they're not the drastic problems with Kerberos that most of the/. crowd is complaining about.
Slashdot Mirror
Implementing these in a subclass requires you to ensure that the objects you are working on belong to that subclass. Categories allow you to apply your methods to objects returned by frameworks without casting/modifying them.
http://www.tla.org/roomba
The other location of the same material:
http://www.tla.org/roomba
Reminder: If you're considering this, remember that PowerFile is majority-owned by Escient, the company responsible for appropriating the CDDB's content under an aggressively restrictive and monopolistic license.
The NeXT development tools (from which OS X's Project Builder is descended) shipped with multiplatform compilers and libraries, and cross-compiling for 68k, x86, Sparc, and HP PA-RISC (and in theory PPC and Alpha, though never publicly) was a matter of selecting the appropriate checkboxes for the project. (Or adding "-arch i386 -arch m68k -arch hppa -arch sparc" to your (g)cc command line.)
Remember, GCC is built for cross-compilation, and, in this case, Apple controls the OS packaging and is able to supply consistent cross-platform libraries.
Also, FYI, the application bundle format is designed to support multiple hardware architectures as well...
As an intriguing point for this thread, Don Box brought an iBook running OS X to this past summer's TechEd conference to give his presentation on XML/SOAP interoperability... (forgot the VGA adapter cable, though...)
Warning: PowerFile's largest investor (IIRC) is Escient, the company responsible for turning the CDDB into Gracenote.
Amongst GUI clients:
Mulberry (from Cyrusoft: http://www.cyrusoft.com) has Win, Mac, Solaris, Linux clients. It's commercial but worth it.
Has preset identities, which can group an outbound mail "account" and a variety of headers, sigs, and signing/encryption keys. Can configure outbound mail in response to mail in a specific mail "folder" to default to a specific one of these identities.
Automated filter rules are in alpha and need some work, but are almost there.
S/MIME support is planned but not there.
PGP support is in there.
Supports IMAP (full online, offline, or disconnected: offline filing, mailbox creation, etc. work properly), POP and local mailboxes.
Both client and server roles are possible, but some uses require somewhat complex configuration.
/. crowd is complaining about.
Please note that Kerberos _authentication_ is unchanged and *completely* interoperable. The only issue is that any vended service which wishes to use the Microsoft authorization data (which is likely to include many or most Windows-hosted services) must receive and understand the PAC.
Samba can (theoretically) operate as a W2K fileserver, using Kerberos, with no issues. It needs to make authorization decisions based on group membership information derived from some other mechanism, however, rather than basing them on group IDs embedded in the PAC field of the Kerberos ticket.
The reverse is manageable as well -- since the *nix box has no conflicting use for the PAC, it is saved by the (Unix) client which thus presents an appropriate ticket to the W2K-based file server when issued the ticket by a W2K KDC; if the ticket is issued by a Unix KDC, a Windows KDC must exist which trusts the Kerberos realm from which the Unix ticket is issued. However, given that you're connecting to a Windows service, the burden of that is not as high as it might otherwise seem.
The major issue with Microsoft's Kerberos implementation is actually:
1. A Unix KDC operating *without* an additional W2K KDC cannot vend tickets to Windows-hosted services which require the PAC to authorize users. Please note, however, that if a W2K-hosted KDC exists, it can trust the non-W2K KDC's tickets for cross-realm authentication, and use them to automatically grant a W2K ticket for access to the W2K-hosted service. Since most services requiring that authorization data would be Windows-hosted anyway, the major issue becomes:
2. The ability to manage a Unix-hosted service using the Microsoft management tools (i.e., establishing the W2K equivalent of a primary domain controller) cannot be made to exist without disclosure of the PAC format. This blows some of the supposed ease-of-administration benefits of W2K away unless you're running W2K servers.
These are frustrating, and the second might constitute an anti-competitive action, but they're not the drastic problems with Kerberos that most of the