Home > Archive > Cobol > August 2006 > User requirements was Re: Cobol, Cics, Soap
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
User requirements was Re: Cobol, Cics, Soap
|
|
| Clark F Morris 2006-08-08, 9:55 pm |
| On 7 Aug 2006 23:58:52 -0700, patrick.sannes@gmail.com wrote:
>
>Pete Dashwood schreef:
>
>I know you are right. I whish I do everything with small messages, but
>the main problem is, there are some large overviews that need to be
>produced. (This is what the business wants, so I can talk with them,
>but at this moment it is a functional requirement...)
>But if it is not possible to send larger messages, I have to look into
>other options, like MQ. Then I can send it in multiple messages and
>concat them in dotNet.
A more basic question is whether the person requesting the information
should be able to just get some subset of data and perform unknown
manipulations on it. Do the requesters really understand the data?
What are the business uses they will make of the data? What
validation will be done of their extract criteria and subsequent
calculations? This may be the way to go depending on the requesting
community but the difference between almost right and right is a lot
of attention to mind numbing detail and obscure rules. Almost right
may be more than good enough for the purpose but the question needs to
be asked before the genie is let out of the bottle.
Also what are the security implications of being able to download that
much data? It will fit on a USB key. Will there be an audit trail on
the downloads?
>Maybe RPC is also a option, but I think then also youre limitation is a
>commerea (like 32k?).
>
>Patrick
| |
| patrick.sannes@gmail.com 2006-08-09, 3:55 am |
|
Clark F Morris schreef:
> On 7 Aug 2006 23:58:52 -0700, patrick.sannes@gmail.com wrote:
>
>
> A more basic question is whether the person requesting the information
> should be able to just get some subset of data and perform unknown
> manipulations on it. Do the requesters really understand the data?
> What are the business uses they will make of the data? What
> validation will be done of their extract criteria and subsequent
> calculations? This may be the way to go depending on the requesting
> community but the difference between almost right and right is a lot
> of attention to mind numbing detail and obscure rules. Almost right
> may be more than good enough for the purpose but the question needs to
> be asked before the genie is let out of the bottle.
>
> Also what are the security implications of being able to download that
> much data? It will fit on a USB key. Will there be an audit trail on
> the downloads?
>
At this moment these things are not a problem. In our current web app
we also provide them with this data. They work with it... The only
thing is we do it now with EntireX and we call it repeatly (using a TS
q. to store the data temp.). But we are trying to move away from
EntireX and make it webservices. I can do it in the same way, like
request the same service for 3 times (then I can get 2100 records) but
I prefer to do it in one request.
[color=darkred]
|
|
|
|
|