If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Currently you cannot talk directly to the Data Adapter from the client, but you can talk to the Metadata Adapter, through the sendMessage method. The Metadata Adapter will receive a call to notifyUserMessage. Then, the Metadata Adapter could talk to the Data Adapter.

Consider that for enterprise applications, you will probably have a cluster of Lightstreamer Servers and you may want to leverage a server-side middleware (e.g. JMS) to dispatch messages to all your Data Adapters. In this case, you will probably deliver messages from the client to a typical web server component (e.g. a servlet), which will publish the data to the messaging bus. And the Data Adapters will listen to this bus.

The simple technique (i.e. sendMessage + notifyUserMessage + Metadata/Data Adapter communication) is also available with Remote .NET Data Adapters.
You should code your Metadata Adapter as a Remote .NET Adapter too ("NotifyUserMessage" is still provided by the .NET library interface).
Then you can have your Remote Metadata and Data Adapter talk to each other quite easily by loading them in the same Remote Server instance. This is shown in DOCS-SDKs\sdk_adapter_dotnet; see chapter 1.6 in doc\DotNet Adapters.pdf. The sample code shows loading both adapters, though communication between them is not covered.

The full technique (i.e. an intermediate servlet and a message bus) is entirely played outside Lightstreamer. We use it in the PortfolioDemo; see http://www.lightstreamer.com/portfolioDemo.htm, where some raw code is available for the java case.

No, sorry for the confusion; I have now fixed my previous post.
sendMessage is provided by the Web Client Library as a method of the LightstreamerEngine objecthttp://www.lightstreamer.com/docs/cl...ml#sendMessage
A call to sendMessage by your client triggers, on the server side, the invocation of the notifyUserMessage method on your Metadata Adapter; this is supported both for java adapters and (as NotifyUserMessage) for remote .NET adapters.

After fireing ls.sendMessage(message) LS console shows an error "unknown function" or something.
Am I too far from what I am looking for (sending message back to server)?

are you sure that you call the sendMessage method only once the ls object is initiated?
The error you're receiving tells you that the object does not have such method and this make sense because before being a LightstreamerEngine instance your ls variable contains a string

for a quick check try to start with a null ls variable. The error message should change.

This is my function from the push page:
function sendMessage(message)
{
debugger;
ls.sendMessage(message);
}
and I am calling that function from Flex.

When it goes into debug the ls is the LS Engine object. So, that''s not a problem.
I think I need to do something on the server to make it work. Looks like it is the last piece of the puzzle to have my solution working.
Here is my .net code:
DataProviderServer server = new DataProviderServer();
server.Adapter = new SocketToLightStreamer();

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.