By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,972 Members | 901 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,972 IT Pros & Developers. It's quick & easy.

revive the fresh-session stored or apply the re-post first?

P: n/a
I cant really think of a reason why I couldn't pesist all my data from
the previous post first, before applying the repost . Logically, if
you think about it as a container of storage... the data just posted
should be applied against the data which the user just posted directly
before.

agreed?
Jan 9 '08 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On Jan 9, 12:36 am, "jonKush...@gmail.com" <jonKush...@gmail.com>
wrote:
I cant really think of a reason why I couldn't pesist all my data from
the previous post first, before applying the repost . Logically, if
you think about it as a container of storage... the data just posted
should be applied against the data which the user just posted directly
before.

agreed?
I think its safe to say a Session gets applied before a Post :) Duh.
Jan 9 '08 #2

P: n/a
jo********@gmail.com wrote:
On Jan 9, 12:36 am, "jonKush...@gmail.com" <jonKush...@gmail.com>
wrote:
>I cant really think of a reason why I couldn't pesist all my data from
the previous post first, before applying the repost . Logically, if
you think about it as a container of storage... the data just posted
should be applied against the data which the user just posted directly
before.

agreed?

I think its safe to say a Session gets applied before a Post :) Duh.
Hi Jon,

I honestly have no clue what you mean.
What are you describing excactly and what is the problem?
Are you trying to avoid double postings because people hit refresh on
their browser maybe? (Guessing here)

Regards,
Erwin Moller
Jan 9 '08 #3

P: n/a
On Wed, 09 Jan 2008 09:36:49 +0100, jo********@gmail.com
<jo********@gmail.comwrote:
I cant really think of a reason why I couldn't pesist all my data from
the previous post first, before applying the repost . Logically, if
you think about it as a container of storage... the data just posted
should be applied against the data which the user just posted directly
before.
It's quite obscure what it is you mean....

Do you per chance talk about 'a user is logged/timed out at the moment he
does a post, he can log in there, and on a succesfull login his previous
post gets applied?'
--
Rik Wasmus
Jan 9 '08 #4

P: n/a
On Jan 9, 1:35 am, "Rik Wasmus" <luiheidsgoe...@hotmail.comwrote:
On Wed, 09 Jan 2008 09:36:49 +0100, jonKush...@gmail.com

<jonKush...@gmail.comwrote:
I cant really think of a reason why I couldn't pesist all my data from
the previous post first, before applying the repost . Logically, if
you think about it as a container of storage... the data just posted
should be applied against the data which the user just posted directly
before.

It's quite obscure what it is you mean....

Do you per chance talk about 'a user is logged/timed out at the moment he
does a post, he can log in there, and on a succesfull login his previous
post gets applied?'
--
Rik Wasmus
Yeah, thats pretty much it. I had gotten myself confused, and
apparently everyone else. I am dealing with various sets of data that
get applied to a user at various states , and I was just unclear at
the moment about whether or not to apply posting data before other
datasets; (i.e. the session). It really was quite silly.
Jan 9 '08 #5

This discussion thread is closed

Replies have been disabled for this discussion.