| Re: Iterative interfacing between client and server [message #169956 is a reply to message #169946] |
Fri, 01 October 2010 15:08   |
Graham Hobbs
Messages: 42
Registered: September 2010
Karma:
|
Member |
|
|
On Fri, 01 Oct 2010 00:12:00 -0400, Graham Hobbs <ghobbs(at)cdpwise(dot)net>
wrote:
> On Thu, 30 Sep 2010 11:52:27 -0400, Graham Hobbs <ghobbs(at)cdpwise(dot)net>
> wrote:
>
>> On Wed, 29 Sep 2010 11:42:38 -0400, Graham Hobbs <ghobbs(at)cdpwise(dot)net>
>> wrote:
>>
>>> On Wed, 29 Sep 2010 07:17:14 -0700 (PDT), Captain Paralytic
>>> <paul_lautman(at)yahoo(dot)com> wrote:
>>>
>>>> On 29 Sep, 04:16, Graham Hobbs <gho...@cdpwise.net> wrote:
>>>> > On Mon, 27 Sep 2010 07:39:07 -0400, Jerry Stuckle
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > <jstuck...@attglobal.net> wrote:
>>>> > >On 9/26/2010 10:06 PM, Graham Hobbs wrote:
>>>> > >> Hello,
>>>> >
>>>> > >> Am still new at this, need to understand a concept before I start
>>>> > >> coding. While the following is an over simplification, at the moment I
>>>> > >> am more concerned with a) 'can it be done', b) preparing a design
>>>> > >> document, so ..
>>>> >
>>>> > >> 1. my website will be driven by server pgm php1
>>>> > >> 2. client accesses the one page website
>>>> > >> 3. client enters/edits data in Forms ( to be javascript edited at
>>>> > >> client machine) then submits
>>>> > >> 4. pgm php1 receives the form data, passing it to a Windows cmd file
>>>> > >> (calling dozens of pgms) for further processing and returning data to
>>>> > >> php1
>>>> > >> 5. php1 then returns the same page to the client with mostly the same
>>>> > >> Form data but with additions and changes
>>>> > >> 6. client views the Form data
>>>> > >> 7. Repeat 3 thru 7 until client happy with results.
>>>> >
>>>> > >> So is my concept:
>>>> > >> - feasible?
>>>> > >> - reflects the way it's normally done (i.e. practical)?
>>>> >
>>>> > >> Please, thanks in advance
>>>> > >> Graham
>>>> >
>>>> > >It can be done. I don't think it's very practical, though.
>>>> >
>>>> > ---
>>>> > Thanks for your answers. So it can be done but my way is not the way
>>>> > to go:-(.
>>>> > not very practical - Jerry
>>>> > it is a bad idea - Shelly
>>>> > not that this makes this idea any better - Capt Para
>>>> >
>>>> > But am not a lot clearer on the 'best way'. Simplifying I hope,
>>>> > suppose a user accesses my one page website, s/he sees unpopulated
>>>> > fields (Forms?) for:
>>>> >
>>>> > Student Number
>>>> > First Name
>>>> > Surname
>>>> > Faculty
>>>> > Major
>>>> >
>>>> > So ..
>>>> > 1. The user enters Student Number, clicks Submit
>>>> > Server uses Student Number to access an sql table
>>>> > Server sends page with first name, surname, faculty, major populated
>>>> > goto 1.
>>>> >
>>>> > Is this a practical web application?
>>>> >
>>>> > Thanks again
>>>> > Graham
>>>>
>>>> So you are suggesting:
>>>> 1) User submits a request.
>>>> 2) Server supplies a response.
>>>>
>>>> This is what every web page in the world does and you are asking if
>>>> this is a practical web application.
>>>>
>>>> I'm sure you can work out that it is.
>>> ---
>>> Yes to your 1 and 2 and is very clear. That's half of what I asked..
>>> What I'm asking is 'can this be an iterative transaction'.
>>>
>>> When I program CICS transactions I give the user a screen, he enters a
>>> student number, a CICS pgm presents the results and sends a populated
>>> screen; user updates some fields clicks Enter, changes are made to the
>>> database, the same screen is represented with an 'update successful'
>>> msg, user makes more changes, enter, database update, represent screen
>>> etc. Then user enters anew student number and the same process occurs
>>> (or user logs off).
>>>
>>> Points are taken with respect to logon ID/password - more scope for my
>>> project.
>>>
>>> OK, maybe my original question might have been 'can I pgm in
>>> php/html/javascript to emulate such a CICS transaction'?
>>> Is this what is being suggested as impractical?
>> ---
>> CP, Jerry, Shelly,
>> CICS eh! Am starting to feel at home:-) .. likely you know too what
>> copybooks are? I will think to your comments especially about the
>> 'cics differences' and will bother you again shortly - sorry .
>> Graham
>>
>> P.S. Have googled, bought a php video tutorial, still not clear on
>> 'calls' so a side question if I may:
>>
>> Being able to call a windows cmd file from my driver php pgm is a MUST
>> for my project (enormously larger than the student record system I
>> used as illustration) .. but I believe I can call a windows cmd file
>> from php and something like this is possible:
>>
>> - block A of some php code
>> - 'call udogen.cmd aparm, bparm' (udogen contains many calls)
>> - block B of more php code e.g 'test return code'
>>
>> i.e. after udogen.cmd has run control returns to block B with a return
>> code.
>> This would work?
> ---
> Folks, I am told it's a bad idea (often:().
>
> Calling other pgms takes too much time before a response gets sent to
> the user - is that one of the reasons? What might other reasons be?
>
> Jerry you say there are differences with CICS - in brief form can you
> tell me what?
>
> I really appreciate all that's being said here - my thanks.
>
> Jerry, CP - since you're CICS'ies any chance I could contact you
> offline - am preparing a little bit of psuedocode that I hope
> illustrates what am trying to do - assuming you have time to look it
> over?
---
Msgs with reasons received with thanks and understood. Will post the
psuedocode here in a few days (need to make sure it's logically
correct).
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]