-
July 21st, 2008, 10:17 AM
#10
Ok, sorry, the error was server side, on the LS console.
The reported message is issued by the default Remote Metadata Adapter (i.e. the LiteralBasedProvider) upon a client message.
In fact, there is no default implementation for NotifyUserMessage.
You have to code a custom Remote Metadata Adapter and use it in place of the LiteralBasedProvider (you can, however, inherit from LiteralBasedProvider).
There, you can put your own implementation for NotifyUserMessage.
(I had to correct again some previous posts; in the .NET interface, the method name starts with a capital letter).
As said in a previous post, your Remote Metadata Adapter should then communicate with your Remote Data Adapter. The best way to achieve this is to run both adapters in the same process. There is no direct support for this, but the provided "StandaloneLauncher.cs" shows an example of a program doing this by leveraging the Lightstreamer.DotNet.Server interface.
Similar Threads
-
By naitsir in forum Client SDKs
Replies: 7
Last Post: October 2nd, 2012, 10:36 AM
-
By hungtt in forum Adapter SDKs
Replies: 7
Last Post: December 30th, 2010, 03:42 AM
-
By naitsir in forum Client SDKs
Replies: 9
Last Post: October 19th, 2009, 04:02 PM
-
By kanibal210 in forum Client SDKs
Replies: 1
Last Post: September 30th, 2009, 08:36 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 03:03 PM.
Bookmarks