And i ll add one thing more! when u get it up, you will see many more alternative implementations will be sumbited to harmony, so let me dream for that :) and it is what we called power of OSS. i mean actually in future we can then replace the implementation of such API's which are based on Service Provider interfaces could be avialable as alternative bases.
On 5/17/05, Sven de Marothy <[EMAIL PROTECTED]> wrote: > > On Tue, 2005-05-17 at 11:46 -0300, Rodrigo Kumpera wrote: > > I'm wondering, some parts of the JDK seens to be product features and > not a > > standard. For examples, the sound system should use arts, esd or alsa (I > > believe Sun support the last 2). The printing system should support > cups, > > lprng or both? > > Such matters are of course not part of the Java spec and are completely > up to the implementation. There would be no point in having a Java API > for these things if a certain underlying API was required. > > > The same goes for the crypto algorithms on the pack. > > No. Although parts of crypto (like so much of the newer APIs) is behind > a Service Provider Interface, you still want to provide everything Sun > does, because applications will expect those algorithms to be available. > > While I'm not sure this is required for strict-TCK compatibility, it is > certainly a compatibility issue for real-world apps. > > /Sven > > -- Usman Bashir Certified IBM XML Solution Developer Certified UML Developer Brainbench Certified Internet Perfessional[advance](BCIP) Brainbench Certified Java Perfessional (BCJP) Brainbench Certified .NET Perfessional Brainbench Ceritified C++ Perfessional (BCCP) Software engineer IT24 Faculty Member Operation Badar Lahore
