To expand on what MikMo said, there are two ways to send data through the serial port - as strings and as bytes.
For a servo, where the position is an angle in the range 0 to 179, the values fit in a byte. so you could send two bytes, and not have to do int to string conversion in Processing. You would also not have to collect the characters into an array on the Arduino, keeping it NULL terminated, and convert the string back to an int.
Sending one value this way requires 1 byte. Sending it as a string requires 1, 2, or 3 bytes ("9", "19", "109").
If the data being sent can not fit in a byte, then conversion to string and back is generally easier to understand than sending the value as multiple bytes and reassembling them on the Arduino.
Some things to keep in mind. Serial transmission is relatively slow. Expecting, in one pass through loop, to collect an entire packet is not a reasonable assumption to make. Therefore, start and end of packet markers make it a lot easier to know where in the byte stream a packet starts and ends.
Also, serial data delivery follows the same guarantee model that the US postal service uses. The system guarantees that it will try to deliver each and every byte. It does not guarantee that it will deliver each and every byte.
So, you must prepare to deal with content loss.
Do you need to send data for both servos every time you send data for one servo? If so, one approach will work (servo 1 data followed by servo 2 data, with, possibly, a delimiter in between). If not, a different approach is needed (which servo is the data for?).