Description of problem:
key input too faster and too much messes up SCIM.

Version-Release number of selected component (if applicable):
scim-1.4.7-34.fc10

Steps to Reproduce:
1.input something too much and too faster
2.
3.
  
Actual results:
discarding the key event or return the same key event regardless of what pressing/releasing the key.

Expected results:
should works expectedly.

Additional info:
Technically it happens when multiple XIM_FORWARD_EVENT is added to the property when the key event is delivered faster than processing it in SCIM. and when it's there more than 4 in the property, it results the same output regardless of what you are pressing/releasing the key. otherwise the key event is discarded.
Why it returns the same key event when the property has something more than 4, IMdkit is getting the value from the property wrongly. a quote from man page:

int XGetWindowProperty(Display *display, Window w, Atom property, long
       long_offset, long long_length, Bool delete, Atom reg_type, Atom
       *actual_type_return, int *actual_format_return, unsigned long
       *nitems_return, unsigned long *bytes_after_return, unsigned char
       **prop_return);
...
long_length
          Specifies the length in 32-bit multiples of the data to be
          retrieved.

and XGetWindowProperty won't delete the property value even if "delete" is True, when there are still unread data.

To do the right thing, read the data with the proper length to not discard the event. and if there are still the unread data in the property, read next data with "long_offset".