What is the proper account to use for icloud?

Question

Do i use my apple id, or my mobileme account? i tried the apple id first and contacts wouldnt sync to icloud from the phone.then i tried my mobile me account info and everything synced. which are we supposed to use?
mobileme account works fine between devices and pc, but wouldnt this stop icloud from accessing my itunes stuff since im not using my apple id?

Answer 1

Sorry to have to tell you this guys but all of the above are broken.
First of all... you should all take a good look at what the read() method actually does.
http://java.sun.com/j2se/1.3/docs/api/java/io/InputStream.html#read(byte[], int, int)
Pay special attension to this paragraph:
Reads up to len[i] bytes of data from the input stream into an array of bytes. An attempt is made to read as many as len[i] bytes, but a smaller number may be read, possibly zero. The number of bytes actually read is returned as an integer.
In other words... when you use read() and you request say 1024 bytes, you are not guaranteed to get that many bytes. You may get less. You may even get none at all.
Supposing you want to read length bytes from a stream into a byte array, here is how you do it.int bytesRead = 0;
int readLast = 0;
byte[] array = new byte[length];
while(readLast != -1 && bytesRead < length){
  readLast = inputStream.read(array, bytesRead, length - bytesRead);
  if(readLast != -1){
    bytesRead += readLast;
}And then the matter of write()...
http://java.sun.com/j2se/1.3/docs/api/java/io/OutputStream.html#write(byte[])
write(byte[] b) will always attempt to write b.length bytes, no matter how many bytes you actually filled it with. All you C/C++ converts... forget all about null terminated arrays. That doesn't exist here. Even if you only read 2 bytes into a 1024 byte array, write() will output 1024 bytes if you pass that array to it.
You need to keep track of how many bytes you actually filled the array with and if that number is less than the size of the array you'll need pass this as an argument.
I'll make another post about this... once and for all.
/Michael