On May 3, 2009, at 10:10 AM, Eric Lyon wrote:
I think that isn't going to be 100% possible. For one thing, any code that uses server sync could be problematic because it will have to wait for the /synced message to come back. Another problem would be code that triggers actions based on server node notifications (/n_go, /n_end etc.). If you're collecting messages but not actually running them on the server, then the notifications never come back and the code wouldn't work. Some methods use server sync internally so a user could very easily depend on it without realizing it. Not to say it's impossible to make the interface cleaner, but with the current architecture, it will be impossible to have total parity. hjh : H. James Harkins .::!:.:.......:.::........:..!.::.::...:..:...:.:.:.:..: "Come said the Muse, Sing me a song no poet has yet chanted, Sing me the universal." -- Whitman |