move camera or objects?

Hmmmm, no one has commented.

Does anyone think that this might be posted in the wrong forum?

Or am I not being clear enough on what I am asking?

Probably no answers since gamedev.net has been down for a while today(and was flacky yesterday). And for your question, moving the camera is normally implemented (or can be thought of as being implemented) as moving all the objects with one of the matrices the object gets transfered by (the modelview matrix in opengl). So they're the same thing. But
If your idea of moving objects is editing their vertices, then it's a bit different (basically it's harder and slower in most cases). But you could implement a camera by moving the vertices if you really wanted.

It's probably easier (and faster) to use what ever camera calls your api has (glulookat is one in opengl) to move all the objects (or move the camera which are functionally the same).

Note: It's usaully more useful from a design standpoint to keep the concepts of moving objects and the camera seperate, even though they're the same functionally.

to me it seems like a ill posed question. moving your camare IS moving the world, that's just how the math works.

Tim