Yes true, I do not expect CakePHP to add any data to session for
me...I guess I thought that if I do a $this->set() or $this->data, it
will be automatically saved for me and accessible in other
requests...now I know it is a wrong assumption (:
Thanks for the $this->Sessison->write() tip.
Thanks
$this->Session->write()
You certainly would not expect cake to add any data to session for
you?
On Sep 5, 1:51 pm, Mona <[EMAIL PROTECTED]> wrote:
> Hi everyone:
>
> I guess I thought CakePHP will have an easy way to store data between
> client requests for the same controller class, but it soun
Hi everyone:
I guess I thought CakePHP will have an easy way to store data between
client requests for the same controller class, but it sounds like
there isn't a built-in way (via $this->set or $this->data) and I have
to store the info into the session myself...
Is this conclusion correct?
tha
Hi Mark:
I tried to store it in various ways, this $this->set, via a class
variable, via a static variable...but nothing worked...
Mona
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to th
I don't know what your application flow looks like and what needs to
be invoked in which order.
You usually want to keep it simple though and only work within one
action during a sinlge request.
function methodA() {
$this->data = $this->__processData();
}
function __processData() {
On Sep 4, 3:20 pm, Mona <[EMAIL PROTECTED]> wrote:
> Hi Jaime:
>
> I tried your suggestion but it didn't work, probably because the calls
> to these 2 methods are from 2 separate client requests.
>
> To answer your last question:
>
> methodA shows a form and handles the form by calling a web servi
Hi Jaime:
I tried your suggestion but it didn't work, probably because the calls
to these 2 methods are from 2 separate client requests.
To answer your last question:
methodA shows a form and handles the form by calling a web services to
retrieve information. methodB is intended to display the
I'm assuming you're not calling methodA and methodB from the same
request from what you've said above.
Really depends on the type and amount of data you're talking about...
you could save the data into the session variable in methodA and pick
it up in methodB during a subsequent request.
Or you
I'm not sure if I'm understanding you correctly, because seems to be
trivial:
class my_controller extends AppController {
var $data;
function MethodA() {
$this->data = 'hello world';
}
function MethodB() {
die($this->data); // hello world.
}
}
Or even:
class my_controller extends AppContro
Hi: I'm using 1.1.19* and have a simple question that I cannot find
answer to from either manual or search here...
I have 2 methods in a controller, let's call them methodA and
methodB. In methodA, I do some work and I want to store the result of
that work so that methodB can access and display
Hi: I'm using 1.1.19* and have a simple question that I cannot find
answer to from either manual or search here...
I have 2 methods in a controller, let's call them methodA and
methodB. In methodA, I do some work and I want to store the result of
that work so that methodB can access and display
11 matches
Mail list logo
