Snapshot is a flag or value?

[chickendev]

Thanks for reply, but I want to ask, why my client cant receive real-time data ? Because from server sides my FeedSimulator still working and update data. What problems here. Again, I am using Lightstreamer-example-StockList-adapter-dotnet get from your Github
with some modify in src/src_data_adapter/StockList.cs:
- Line 79 to: // _myFeed.SendCurrentValues(itemName);
- Line 106 to: return false;

[giuseppe.corti]

Hi chickendev,

So your problem is that you have changed the Data Adapter code, such that it no longer provides the snapshot, but then you also no longer receive the normal real-time updates?
First, your changes to remove the snapshot management from the Data Adapter seem correct to me.

Let me recap what the scenario should look like in your case:

1. a client subscribes for the first time an item of the StockList demo, let's say item1;
2. the Lightstreamer server receives the subscribe request and asks the Data Adapter for the snapshot;
3. the Data Adapter reply false to IsSnapshotAvailable
4. the Lightstreamer server dispatches an EndOfSnapshot event to the client
5. when the ExternalFeedProducer of the adapter produces a new update for item1 the Data Adapter pushes it into the Lightstreamer server
6. the Lightstreamer server sends the update to the client, unless it is filtered for some reason (that can be either an exceeding of the frequency limit imposed for that client or the outgoing queue for that client is full).

Then 5. and 6. repeat until the client unsubscribes item1.

Now it is necessary to understand in your case what is actually missing if only point 6. or also points 4. and 5.
Please could you reproduce the issue after changing these log settings (lightstreamer_log_conf.xml):

<logger name="LightstreamerLogger.requests" level="INFO"/>
<logger name="LightstreamerLogger.subscriptions" level="DEBUG"/>
<logger name="LightstreamerLogger.subscriptions.upd" level="DEBUG"/>
<logger name="LightstreamerLogger.pump" level="DEBUG"/>

then the lightstreamer.log should provide useful information to understand what is going wrong.

Regards,
Giuseppe