Parameters to image.php

[Mathijs]

Hi,

I generate images on the fly. I need to pass parameters to the image-script
(image.php). The parameters are larger than 255 characters.

What's the best way to pass large parameters from the calling page (<img
src="image.php">) to the image.php script? Cookies? Filesystem?

Thanks in advance for the suggestions.

M.

[ZeldorBlat]

>What's the best way to pass large parameters from the calling page (<img

src="image.php">) to the image.php script? Cookies? Filesystem?

POST

[Erwin Moller]

Mathijs wrote:

Hi,

I generate images on the fly. I need to pass parameters to the
image-script (image.php). The parameters are larger than 255 characters.

What's the best way to pass large parameters from the calling page (<img
src="image.php">) to the image.php script? Cookies? Filesystem?

Thanks in advance for the suggestions.

M.

Hi,

Depends on the situation.

If you have a few simple things to send by the client, just use POST.

If you have a huge page where you also display results that have some
correlation to the image, you might consider using a SESSION to store the
data in you use for imagegeneration.
In that way you avoid double calculations and database-queries.

Regards,
Erwin Moller

[Mathijs]

29 nov 2005 ta (Erwin Moller) shuo le:

If you have a few simple things to send by the client, just use POST.
If you have a huge page where you also display results that have some
correlation to the image, you might consider using a SESSION to store
the data in you use for imagegeneration.
In that way you avoid double calculations and database-queries.

It's just a simple thing: a want to send a gamerecord to the image.php
script and with that data, I want to draw a board.

Currently, the image-script gets triggered by the <img src="image.php">
construction? Don't I need an action (form) to 'post' variables?

TIA,
Mathijs.

[Oli Filth]

Mathijs wrote:

29 nov 2005 ta (Erwin Moller) shuo le:

If you have a few simple things to send by the client, just use POST.
If you have a huge page where you also display results that have some
correlation to the image, you might consider using a SESSION to store
the data in you use for imagegeneration.
In that way you avoid double calculations and database-queries.

It's just a simple thing: a want to send a gamerecord to the image.php
script and with that data, I want to draw a board.

Currently, the image-script gets triggered by the <img src="image.php">
construction?

In that case, store the game record data in $_SESSION.

--
Oli

[Erwin Moller]

Mathijs wrote:

29 nov 2005 ta (Erwin Moller) shuo le:

If you have a few simple things to send by the client, just use POST.
If you have a huge page where you also display results that have some
correlation to the image, you might consider using a SESSION to store
the data in you use for imagegeneration.
In that way you avoid double calculations and database-queries.
It's just a simple thing: a want to send a gamerecord to the image.php
script and with that data, I want to draw a board.

Currently, the image-script gets triggered by the <img src="image.php">
construction? Don't I need an action (form) to 'post' variables?

Yes, you do, you are right.
You should use GET for simple stuff.

I don't think you should care too much about the 255 characters.
It is depends on the server if it can handle a big url, and any modern
webserver can do so these days.

I would advise you to just put the whole bunch of data after the url.

Regards,
Erwin Moller


TIA,
Mathijs.

[Mathijs]

29 nov 2005 ta (Oli Filth) shuo le:

In that case, store the game record data in $_SESSION.

Aye, sir!

Thanks all.

Cheers,
M.

[Mathijs]

29 nov 2005 ta (Erwin Moller) shuo le:

I would advise you to just put the whole bunch of data after the url.

It can really get long (it's a long game:). Is there a theoretical limit to
the length of get-vars on modern servers? I think I'de rather take your
first advice: sessions.

Thanks.