Recent

Author Topic: Tracking Client ID  (Read 3266 times)

guest48180

  • Guest
Tracking Client ID
« on: June 08, 2018, 08:47:54 pm »
I track clients across web pages using their client ID set in a $_SESSION["variable"]. Is there a similar mechanism in Lazarus to track clients connecting to a remote database?

Thaddy

  • Hero Member
  • *****
  • Posts: 14204
  • Probably until I exterminate Putin.
Re: Tracking Client ID
« Reply #1 on: June 08, 2018, 09:44:11 pm »
Even better, does not need cookies. Store the IP serverside. (Cookies are technically never needed for session maintenance)
Specialize a type, not a var.

guest48180

  • Guest
Re: Tracking Client ID
« Reply #2 on: June 09, 2018, 12:31:03 am »
That works for me.

ASerge

  • Hero Member
  • *****
  • Posts: 2223
Re: Tracking Client ID
« Reply #3 on: June 09, 2018, 04:17:28 am »
Even better, does not need cookies. Store the IP serverside. (Cookies are technically never needed for session maintenance)
Client IP?
What about PAT (port address translation, or IP masquerading or NAT overload and many-to-one NAT). Many clients from one IP.

guest48180

  • Guest
Re: Tracking Client ID
« Reply #4 on: June 09, 2018, 06:31:36 am »
Already got it whooped! :D

Thaddy

  • Hero Member
  • *****
  • Posts: 14204
  • Probably until I exterminate Putin.
Re: Tracking Client ID
« Reply #5 on: June 09, 2018, 07:45:31 am »
Even better, does not need cookies. Store the IP serverside. (Cookies are technically never needed for session maintenance)
Client IP?
What about PAT (port address translation, or IP masquerading or NAT overload and many-to-one NAT). Many clients from one IP.
It is not a web but a networking scenario as I understand it. Usually you can use the IP as a fingerprint for a session, maybe + pw hash and/or certificate (result) .
The scenario is for authentication, not location as such.
« Last Edit: June 09, 2018, 07:59:34 am by Thaddy »
Specialize a type, not a var.

guest48180

  • Guest
Re: Tracking Client ID
« Reply #6 on: June 09, 2018, 12:53:59 pm »
Exactly. This is all abt tying client_id to the client, making sure they access only their records.

Anyway, I wanted to use several forms for this application. And doing it that way meant I'd have to pass the client_id from form to form for the various queries. But since I can't figure out how to do that, I settled on just using a TPageControl component. I don't like this approach as much. But until I know how to work it out another way, this will work.

 

TinyPortal © 2005-2018