In this case, some trickery with matrices is needed - on ancient Fixed function we generated projection coordinates with glTexGen and parameter GL_REFLECTION_MAP. How to compute the exact coordinates is described here - http://www.opengl.or...ics_of_glTexGen

First compute vector from eye to vertex (as described here - gl_ModelViewMatrix * gl_Vertex) and normalize it.Then compute eye normal that would be gl_NormalMatrix * gl_Normal and compute 2 times dot product of eye normal vector and eye normal vector, in the end generate all three coordinates as described in code, in GLSL it might look as:

Note that reflection_coord is vec3 going out to geometry and/or fragment shader (pixel shader), I also don't remember if you didn't have to do eye_vert.xyz = eye_vert.xyz / eye_vert.w; although it should be (according to OpenGL.org wiki correct, and also I didn't have time to test it with built-in matrices, as I build my own matrices that I pass to glsl and I'm not using built-in ones).

EDIT: Sorry, my mistake - I was thinking it is cubemap reflection (my appologize, I actually posted in wrong forum and realized just today ... could mod please delete this post (when reading this)? It's definitely not related, Thank you ... ) I wonder if I can report myself? And also note that there isn't working function of delete your own post on forum...

Do you mean its not changing when you move the camera, or turn the camera?

Its not clear from your code why you think turning the camera should change the output.

Yeah. Sorry. I meant when the camera is exactly turned. I thought that it should change because of that. I saw that in many games.

EDIT: Sorry, my mistake - I was thinking it is cubemap reflection (my appologize, I actually posted in wrong forum and realized just today ... could mod please delete this post (when reading this)? It's definitely not related, Thank you ... ) I wonder if I can report myself? And also note that there isn't working function of delete your own post on forum...

That's OK! This still might be helpfull some time after. When i will finish my "CryEngine" killer and rule this world!

As karwosts said, and as your code shows, specular is based in the position of the camera, position of the fragment and the normal. When you turn the camera, it should not change.

Perhaps there is some missunderstanding caused by me. Sorry about that.Right now i'm testing my scene with a "chase" type camera. That means it's turned around the object.This is the video that shows what i'm talking about:http://www.youtube.com/watch?v=jz3aDUJFOdcIt was made in one of the engines i used. Light source is directional and stationary.What i want to achive is something similar with the same conditions - turning the camera around the object - specular should move. Right now it's stays still regardless of camera position around it (can't make another video right at this moment).

As you move the camera, check that the value you set for LightDirection remains constant, and that the value you set for CameraPosition changes. You might accidentally be computing these in camera space, instead of world space.

I've checked them with gDebugger and it seems that lightDirection is constant and cameraPosition changes.
Perhaps there is something wrong with the CPU part of code. I just wanted to verify that my shaders are correct. If that's so, then i will be looking at the other end.