Now uses String based IDs which are specified in publish. There is no need to create a topic prior to publishing to it.

About to try drastically modifying the service.

Remove synchronous PubSubClient.CreateTopic API from Silverlight client: http://laharsub.codeplex.com/workitem/4

Diapatch asynchronous callbacks in the PubSubClient on the same thread type as the asynchronous operation was initiated: http://laharsub.codeplex.com/workitem/5

Fix NullReferenceException in Silverlight PubSubClient: http://laharsub.codeplex.com/workitem/3

Fixing client side race condition in the http long poll abort logic: http://laharsub.codeplex.com/workitem/2

Merge into default branch for the first stable release

Unit test and solution fixes

Improve consistency check reporting

Fix bug in LoadTestClient parameter processing

Adding stress mode to LoadTestClient

Changing default message TTL to 15s

Fix race condition in bookmarks resumption logic, release handles

Adding retry logic to LoadTestClient

Bookmark and memory management improvements in InMemoryPubSubBackend

Enhancing performance report content

Increasing time measurement precision in LoadTestClient

Lock contention imrovement in the bookmark resumption logic in InMemoryPubSubBackend

Reduce thread pool lock contention in bookmark resumption logic in InMemoryPubSubBackend

Change performance test client to not use HTTP proxy or Expect-100-continue

Refactoring publish and create topic code in PubsubClient

Converting PubsubClient from using WebClient to HttpWebRequest

Merge

Improvements of HTTP request resources cleanup in the PubsubClient

Optimizing data structures and lock scopes in the InMemoryPubSubBackend