|
>From: Brad Stone [mailto:brad@bvstools.com] >"Web" vs. "in house" is what I said. I don't mean to imply public accessibility, internet access, or any other Amazon-like delivery other than the sole requirement that the client-side install be limited to a web browser and the server supply HTML. Are you saying that a "browser based" in-house system can't handle it? >Unless you're selling one item with no options, things get tricky. Sure. But they get tricky anywhere. They are more tricky in 5250, in VB, in Java or in HTML. >What you will present to the web user and what your CSR will want as far as detail will differ. >...the level of detail that they want is much more than a user on the web will require. Sure, and they will use different browser-based apps. I'm not suggesting that what works for me as a customer of a company works for internal CSRs, simply that the internal app can be browser-based. >I also think a GUI may be the solution Isn't a web browser GUI? I don't mean to beat a dead horse. And this customer may indeed have some special need that can only be satisfied by a fat-client. However, given Aaron's statement that he's been asked to "look into...GUI" and that he's "planning on using CGIDEV2 to start" I assume that the current solution is 5250 based. I find it hard to believe that there is something that a 5250 based solution could deliver that a HTML-based one couldn't. I'm talking about functionality, not interface, so don't tell me that a browser can't handle F23, I know that. However, the same _functionality_ could be achieved with a hyperlink. -Walden ------------ Walden H Leverich III President Tech Software (516) 627-3800 x11 (208) 692-3308 eFax WaldenL@TechSoftInc.com http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) -----Original Message----- From: Brad Stone [mailto:brad@bvstools.com] Sent: Tuesday, August 13, 2002 17:19 To: web400@midrange.com Subject: Re: [WEB400] Customer Service -- Online Ok, one last time... > >Because I know the people and business that he's > building this for very > well. > > Fair enough. Perhaps they are indeed a special case. > Let's ignore this > special case. It's not a special case. As I will try and explain again... > > >...web works great for simple order history... > >But in-house...things get a little complex. > >Not a great fit for web. > > I'd be curious why you feel complex data isn't a great > fit for the web. Yes, > I admit there are some things that aren't made for the > web. These would > include interfacing with client-side hardware (scanners, complex > printers, handhelds, etc), complex graphics operations (GIS type > stuff, CAD, Photo > editing, etc.) and system level operations (disk defrags, > anti-virus > software, etc.) However, for the kind of stuff we all do > (with iSeries > backgrounds) I think it can be all handled with a > browser[1]. I'm not talking hardware or interfaces. Business rules. > I'm curious why you > think that anything more complex than a simple order > history is beyond the > capabilities of browser-based interfaces. I didn't say that. You're putting words into my mouth and reading too much into my statement. "Web" vs. "in house" is what I said. Unless you're selling one item with no options, things get tricky. What you will present to the web user and what your CSR will want as far as detail will differ. That's all I'm saying. But not in all cases as you pointed out. And we're full circle back to Aaron's original question.. I know the CSRs, I know the business, and I know the level of detail that they want is much more than a user on the web will require. I also think a GUI may be the solution, I never made a definate suggestion for that, I told him it may be worth looking into. Brad _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/web400 or email: WEB400-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
