One of the major limitation of SharePoint 2010 Client object model is that that it does not support SPSecurity.RunWithElevatedPrivileges.
Since you're code runs on the client, the identity can not be reverted to the application pool account. Running code as system account via the client object model would open a security hole and then everybody could write and execute code as an administrator.
PS : SharePoint 2010 Client Object Model does not support RunWithElevatedPrivileges.
One of the major limitation of SharePoint 2010 Client object model is that that it does not support SPSecurity.RunWithElevatedPrivileges.
Since you're code runs on the client, the identity can not be reverted to the application pool account. Running code as system account via the client object model would open a security hole and then everybody could write and execute code as an administrator.
PS : SharePoint 2010 Client Object Model does not support RunWithElevatedPrivileges.