[Bollaroid II]

http://www.javaworld.com/javaworld/j...019-jxta.html?

Part of Apple's comeback strategy was to adopt standards used by pc makers and only push their own standard when it was obviously better than what is currenlty available.

Instant messaging is goig to take off. Whether it will be the killer revenue generating app that is being touted by M$ I do not know, but it is definitely going to become a part of everyday life.

Apple would do well adopting this standard because it was designed from the ground up to be for p2p, highly secure, language and platform independant. In other words it has both the advantages of Java $ .NOT.

This is unlike other products that are product-oriented(i.e. what products do we have and how to solve new solutions and leverage those products). Rather it is solution focused - we want to be able to do x, high are we going to do it.

The fact that implementations in Java exist is just because Sun has chosen to do an implementation, otherwise the implementation is just that, not part of the platform. This is good because Apple could create its own implementation that is scriptable & expandable using its own native tongues - Applescript and friends.

[Bollaroid II]

Originally posted by Bollaroid II:
<STRONG>http://www.javaworld.com/javaworld/j...019-jxta.html?

Part of Apple's comeback strategy was to adopt standards used by pc makers and only push their own standard when it was obviously better than what is currenlty available.

Instant messaging is goig to take off. Whether it will be the killer revenue generating app that is being touted by M$ I do not know, but it is definitely going to become a part of everyday life.

Apple would do well adopting this standard because it was designed from the ground up to be for p2p, highly secure, language and platform independant. In other words it has both the advantages of Java $ .NOT.

This is unlike other products that are product-oriented(i.e. what products do we have and how to solve new solutions and leverage those products). Rather it is solution focused - we want to be able to do x, high are we going to do it.

The fact that implementations in Java exist is just because Sun has chosen to do an implementation, otherwise the implementation is just that, not part of the platform. This is good because Apple could create its own implementation that is scriptable & expandable using its own native tongues - Applescript and friends.</STRONG>

sorry for the spelling mistakes . here it is revised:

Originally posted by Bollaroid II:
<STRONG>http://www.javaworld.com/javaworld/j...019-jxta.html?

Part of Apple's comeback strategy was to adopt standards used by pc makers and only push their own standard when it was obviously better than what is currenlty available.

Instant messaging is going to take off. Whether it will be the killer revenue generating app that is being touted by M$ I do not know, but it is definitely going to become a part of everyday life.

Apple would do well adopting this standard because it was designed from the ground up to be for p2p,is highly secure, language and platform independant. In other words it has both the advantages of Java & .NOT.

This is unlike other products that are product-oriented(i.e. what products do we have and how do we solve new solutions and leverage those products at the same time - MS design guideline). Rather it is solution focused - we want to be able to do x, how are we going to do it.

The fact that implementations in Java exist is just because Sun has chosen to do an implementation, otherwise the implementation is just that, not part of the platform. This is good because Apple could create its own implementation that is scriptable & expandable using its own native tongues - Applescript and friends.</STRONG>