TwinTurbo.NET: Nissan 300ZX forum - Re: No, not at all. The same could be said of you.
People Seeking Info
 
   


     
Subject Re: No, not at all. The same could be said of you.
     
Posted by Kenny on August 05, 2005 at 2:17 PM
  This message has been viewed 29 times.
     
In Reply To No, not at all. The same could be said of you. posted by Moxie on August 05, 2005 at 01:49 PM
     
Message It was more just that you don't seem to be interested in
actually having a discussion, you would rather take shots at me, so why even try?


But if you want a response, then okay, here it is:


"If a user on a system expects a certain results set returned from a system
call"


Database queries and system calls are not the same
thing.


-When a user, let's say an SAP user, queries his system,
let's say for some customer information, That information may or may not exist
in SAP. SAP may make a connection to a middleware layer to retrieve specific
information. This middleware layer may gather the pertinent information from
various other backend systems, whether they be a database or flat files or some
custom application that sits on the backend that takes requests and returns
data. So, when the user makes a system call (semantics here, maybe you are thinking
of a low level system call) s/he may be actually accessing dozens of systems
without even knowing. For all s/he knows, they just clicked okay and expect
a result to be returned, when it doesn't properly, there's a problem e.g. an
idex issue on some backend system


That explanation has nothing to do with differentiating
between a database query and a system call.


"and it doesn't return that expected results set, it's
broken and not working properly, regardless if it's just an index is out of
date. The backend functionally is considegreen a blackbox to the frontend user."


The backend of an application is the database, the front-end is the GUI and the corresponding code that interfaces with the backend, not the user.


- Yeah, sure, but 100% of the time. This may be true
for a single application, when talking about distributed systems, a backend
could be various things, not necessarily just a database. The frontend user
is the person that would sitting down at the computer interacting with the frontend
GUI


In the case of TTNet, we are talking about a
database backend. Nice backpeddling on the "frontend user."


"So I agree with you, but I am saying, trust me, in the
real world, if an index is off, it's the same thing to say it's broken from
a frontend user."


Front-end user again?


- Not sure what you are trying to get at?


The fact that you again implied the user was
the frontend.


"assumed you would understand what I was talking about
since you seem to be an expert. But what do I know? I only work for the Department
of Defense designing Enterprise Level software applications."


The other programmers must laugh in your face. Designing software applications for the DoD isn't much to brag about. At least I never have.


No, actually, I haven't had too many people laugh at my
face, maybe they do it behind my back?? The current project I am on is extremely
exciting and dynamic. Maybe you've been on a bad project with the DOD, but Distributed
System Development is extremely fun and challenging. I like it, so I guess that's
all that matters. Although, I am about to roll off the project and work on some
B2B Webservices type stuff, I am excited about doing that as well.


Congratulations.

mkay?
Kenny...

PETZ Member #5


SteamyZ. Never had did me wrong. - SL103 07/06/04 11:58:15

     
Follow Ups  
     
Post a
Followup

You cannot reply to this message because you are not logged in.