problems: DB connection,parameters,groups

hi all, i test lightstreamer moderato on my localhost (win xp). i run the Hello World sample this work well.

from this example the following problems arise:
1.- i modified the code to make connection with the Data Base DB (mysql). When i do the debug the code (on eclipse) all works fine, i get info from the DB, but when i run this on a browser, i don't get any result :( the page gets the first messages "loading..." all the time.
i use "mysql-connector-java-5.1.7-bin" to connect to the DB and i add this to the class path of the sistem. What is the problem??? i need to know if the solutions works on linux centos.

2.- how can i send parameters from the browser?? the idea is to send the user name to obtain data associated with that user. Do they have an example on this? where can i get information about this?

3.- the last questions is, how can i do to push data to a specific group of users??

thanks for your help.
pd. sorry for my english.
NaiTsiR

i again,

about the first problem i see in the lightstreamer shell that the class can't found the driver to open a connection with the DB. i don't understand why this happend, because i add to the classpath the path of the jar file.

i see is necessary to add the library into the LS server, i do some test to add the jar file in some folders and the problem is solved :D i add "mysql-connector-java-5.1.7-bin.jar" into /shared/lib/ folder and all works fine.

about the other two questions, somebody can helpme??

regards

hi,

you could use the setUserName (and setPassword) method of the javascript libraries to identify your user. Such information is received by your metadata adapter in the notifyUser method.
If the notifyUser method exits succesfully, ie the user is authenticated, (and the client subscribes to some item) you'll receive getItems calls that contain such user name. There you can customize the item names sent by the clients so that each user subscribes to a different item(s).

I think that this answers both your questions, let me know if you have any doubt.

Hi Mone,
thanks for your answer, i try this today and keep you informed

see you.

hi Mone again :)

i have a doubt, is there any way to send the username and password from apache server to lightstreamer server?? i don't like javascript working with importan data.
perhaps a way to protect that informations is encrypted, but i would avoid manipulate it with javascript.

see you

You are not required to issue the apache credentials to Lightstreamer through javascript.

See this FAQ for our guidelines.

thanks for your reply,

to see if i could understand, is possible to authenticate from my web server on lightstream server to obtain a session id, then my web server send this session id to the client (brower) and the client send the session id to lightstreamer server.

is that correct??

do they have a practical example of this??

regards.

Yes, I forgot to mention that the general concepts document,
that you can find in Lightstreamer package in DOCS-SDKs,
also covers this topic in paragraph 4.1.
It's not a practical example, but there is a diagram to illustrate the scenario.

I'm not sure we are saying the same thing.
The Web Server does not authenticate on Lightstreamer Server: it's the other way round.
The temporary session id supplied by the Web Server to the pages is visible and can be manipulated by javascript and sent to Lightstreamer Server as a username or password.
In order to validate it, the Metadata Adapter has to inquiry the Web Server.

thanks, i will review the documents that mention me, i have a few doubt about this, i'll see if i can solve and they discussed the results.

see you

i checked the documentation and i'm not happy to send the username and password via javascript :(
is there a way to protect this information? i thought about sending this information encrypted and decrypt this in the java adapter. but i prefer there is another safer way.

see you and thanks for your help.

hi,

did you check page 15 of the document suggested by Dario?
We're suggesting to authenticate your user with an SSL connection against your web server, than you'll send to lightstreamer a token (usually the session cookie) generated by the web server, not the password.
Once such token reaches your metadata adapter you'll validate it against your web server.

yes, i read this page, according to the diagram, i see it's necessary to send the username and password at least once, then the LS server send to the cliente a session_id.

about the SSL connection, is there any way to send the information with https?? regardless that the master push page has been dowloaded through https or not.

thanks for your help

Hi,

Quote:

---

yes, i read this page, according to the diagram, i see it's necessary to send the username and password at least once, then the LS server send to the cliente a session_id.

---

if you check the image on page 15 (attached) you'll see that the first request from the client goes to the web server not to Lightstreamer server. Such request can be a https request that contains the user and password.
You will authenticate the user on your web server. The web server will send its session id to the client in some way (usually within a cookie).
This first part has no relation with Lightstreamer, is just a classic web authentication.

Once the client is authenticated on the web server it will open the stream connection to Lightstreamer server but, instead of sending user and password to such Lightstreamer server, it will send user and the session id generated by your web server.
The metadata adapter will receive such info and will in turn communicate with your web server to ensure that the user/session id pair is a valid one and in such case will enable the streaming session.

So, no password is sent to the Lightstreamer server, only the user and a session id generated by your web server.

Quote:

---

about the SSL connection, is there any way to send the information with https?? regardless that the master push page has been dowloaded through https or not.

---

no, you can open an https streaming session only from a https page

thank you very much for your answers, are highly informative.
i try to implement this, is a bit difficult because i don't have practical examples :(

see you and thanks again