Some questions I have for Apple.
Steve
- In Tiger, will the maximum size of a process move past 4GB? Will it move to be 64-bit or 42-bit?
- When will the L1/L2 cache size on the G5 increase? I'm cool with having to buy an Xserve to get that.
- Will you please improve the public API for NSStatusItem? There's some stuff I want to DO with that sucker.
- Will all of Tiger be firmly based on FreeBSD 5.1 or will it be a 4.8/5.0 split like it is now?
- Somebody noted recently that non-threadsafe libraries from FreeBSD 4.8 are expected to play nice in the threaded XNU kernel. Is this true?
- When will Apple's SOAP support be updated to conform to the WS-I Basic Profile 1.0? Some of us are using the document/literal form of SOAP and it's really nice.
- Hey, can I have some better tools for managing my processes? Specifially, I'd like to see Solaris' priocntl and dispadmin ported. I think I can see process scheduling classes when using the ThreadViewer, I want more!
Steve
![[RSS 1.0 Feed]](/osx/valid-rss.png)
2 Comments:
And when will the AppleScript SOAP support handle https transports and Basic Authentication? (If you specify a username and password in the url, it simply ignores them and connects anyway, radar Problem ID 3532847...)
_Mark_ <eichin@thok.org> http://www.thok.org/bloggery/
By Anonymous, at 10:10 PM
I'm curious about your motivation for asking about 42 vs 64 bits of addressability. At this time, 512 Gb (42 bits) would not be an unreasonable upper-limit for Apple's market -- if you were to need more than that, I'd look to some serious iron from IBM. 2,147,483,648 Gb (64 bits) -- well that should do for anybody today. If you program 64-bit clean, then any internal limits (that may or may not exist) on the amount of addressable memory will be transparent to you and Apple can expand what is possible as the need arises.
On the other hand, if you motivation is curiosity, well, who could question that? ;-)
By Travis, at 10:48 PM
Post a Comment
<< Home