continued from above thread
09:11:01,270 |DEBUG|Logger.METADATA |SERVER POOLED THREAD 10 |New Session S4abfa93fa2681585T1101270 for user ad04d127-55a3-454a-a628-cd00fe3408be from 10.41.220.7
09:11:01,270 |INFO |Logger.METADATA |SERVER POOLED THREAD 10 |User ad04d127-55a3-454a-a628-cd00fe3408be has 1 concurrent session(s) after this new session S4abfa93fa2681585T1101270 added.
09:11:09,195 |DEBUG|Logger.METADATA |SERVER POOLED THREAD 8 |notifySessionClose: session id is S4abfa93fa2681585T1101270
server-3.log:09:11:01,272 |INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 10 |Starting new session: S4abfa93fa2681585T1101270 from 10.41.220.7:44852
server-3.log:11-Aug-10 09:11:05,188 |INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 9 |Serving request: /lightstreamer/bind_session.txt?LS_session=S4abfa93fa2681585T1101 270&LS_content_length=50000000&LS_report_info=true &LS_silverlight_version=1.0 from 10.41.220.7:44852
server-3.log:11-Aug-10 09:11:05,190 |INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 9 |Attaching session: S4abfa93fa2681585T1101270 from 10.41.220.7:44852
server-3.log:11-Aug-10 09:11:09,194 |INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 8 |Serving request: /lightstreamer/control.txt?LS_session=S4abfa93fa2681585T1101270&L S_op=destroy from 10.41.220.7:44878
atbt-ams-server-3.log:11-Aug-10 09:11:09,194 |INFO |LightstreamerLogger.requests |SERVER POOLED THREAD 8 |Destroying session: S4abfa93fa2681585T1101270 from 10.41.220.7:44878
second session started
09:11:08,268 |DEBUG|ATBTLogger.METADATA
|SERVER POOLED THREAD 5 |New Session S92957313c3dc0a6eT1108268 for user
ad04d127-55a3-454a-a628-cd00fe3408be from 10.41.220.7

server-3.log:11-Aug-10 09:11:08,268 |INFO |LightstreamerLogger.requests
|SERVER POOLED THREAD 5 |Starting new session: S92957313c3dc0a6eT110826
8 from 10.41.220.7:44878
server-3.log:11-Aug-10 09:11:11,136 |INFO |LightstreamerLogger.requests
|SERVER POOLED THREAD 6 |Serving request: /lightstreamer/control.txt?LS
_session=S92957313c3dc0a6eT1108268&LS_op=add&LS_ta ble=1&LS_id=ADAPTER&L
S_mode=RAW&LS_schema=MESSAGEID+DATA+MESSAGE_TS&LS_ data_adapter=ADAPTER from 10.41.220.7:44889
server-3.log:11-Aug-10 09:11:11,137 |INFO |LightstreamerLogger.requests
|SERVER POOLED THREAD 6 |Controlling session: S92957313c3dc0a6eT1108268
from 10.41.220.7:44889
server-3.log:11-Aug-10 09:11:40,461 |INFO |LightstreamerLogger.requests
|SERVER POOLED THREAD 9 |Polling (2) to session: S92957313c3dc0a6eT1108
268 from 10.41.220.7:44878
-server-3.log:11-Aug-10 09:12:10,702 |INFO |LightstreamerLogger.requests
|SERVER POOLED THREAD 9 |Polling (3) to session: S92957313c3dc0a6eT1108
268 from 10.41.220.7:44878
server-3.log:11-Aug-10 09:12:40,880 |INFO |LightstreamerLogger.requests
|SERVER POOLED THREAD 9 |Polling (4) to session: S92957313c3dc0a6eT1108
268 from 10.41.220.7:44878
.....



So this is what confused me.
1. Why the client issued the second create_session even the first session was still valid on server?
2. Why the second bind_session request submittd as POST and in POLLING mode?
3. Will lightstream automatically subscriber the same items for second session or the application needs to make the call?

Thanks

Eric