NeoMedia Technologies, Inc (NEOM)

[jonesieatl]

bleedingedge / elementus

bleedingedge , thanks again for your input .

We all do appreciate your comments especially since you worked with NeoMedia you know how things 'work' there .

elementus , there still seems to be a difference between what you are saying and what bleedingedge is saying and I think it would be great to resolve this .

bleedingedge's background is such that we certainly have to give at least as much weight to his input as we might to you .

bleedingedge , you said this statement by elementus "Neoreader pass ALL codes via Neom server. Even direct URLs" is an incorrect statement.

elementus , you seem to be continuing to maintain that "Neom want to know all about clicks and therefore each data passes server" , thus implying at least some sort of side-trip to NEOM's servers (perhaps a "hidden function"?) even in the case of a 2D code which contains URL information which would allow the mobile device to jump directly to the target website .

If I am reading you guys right , these are opposing statements . Both cannot be true ?

bleedingedge , is it possible that even though in a 'direct' situation NeoReader could in fact take the mobile device's browswer directly to the URL , there is always a quick trip past a NEOM server to deposit some info so NEOM can "know all about clicks" as elementus maintains? Based on NeoMedia's business feature of providing click-info data to customers I guess I can see where that could be built-in , I'm just trying to understand if it is always built-in.

Thanks for you guys' help if you can resolve this , if not I suppose it can simply be left as a disagreement .... something which goes counter to my engineering "black/white" side lol .

jonesie