|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Waitman
emkdesign.comDate: Tue Oct 02 2001 - 10:20:02 CDT
Greets.
I have had success in the past using the MS Internet Explorer browser
component in a C++ program, then capturing all get/post requests, parsing
them, grabbing the appropriate file - if it is plain html just forward the
file to the browser component. otherwise send the file through a scripting
engine and just send the results to the browser.
You should be able to do likewise in VB or etc.
This method works well with "single user" apps, takes up a lot less
resources than a full blown web server. Plus you can do things like fire up
a database server - just while your program is running.
I have used this method with PHP, PERL and MySQL db server - you can even
get everything to run off a CD without actually installing anything on the
client machine. (if your data can be read-only) otherwise you can partially
put some stuff on the client machine, the stuff that needs updating, etc.
Not sure about ASP, but I reckon it could be a similar task. Just might have
distribution issues.
Best,
Waitman C. Gobble, II
EMK Design
Buena Park CA 90621
714-522-2528
----- Original Message -----
From: "Doug Vallis" <DVallis
uniongas.com>
To: <focus-ms
securityfocus.com>
Sent: Tuesday, October 02, 2001 6:11 AM
Subject: RE: Running IIS locally - advice?
>
> Consider converting the application over to Visual Basic to run local on
the
> laptop. This will preserve most if not all of your code as possible. VB
> supports the development of "web applications" that look and feel like a
web
> based app but all "backend" server code is compiled into the local
> application.
>
> There are far too many security and design flaws with implementing a
> solution like this using a local web server like IIS on as many laptops as
> you are considering. You should rethink the deployment and architecture of
> such an application.
>
> Doug
> -----Original Message-----
> From: dayseizer
excite.com [mailto:dayseizer
excite.com]
> Sent: October 1, 2001 11:35 AM
> To: focus-ms
securityfocus.com
> Subject: Running IIS locally - advice?
>
>
> I have an asp (Active Server Pages) application that I have to deploy
> locally to laptops. The thought process was, let's people used to seeing
> this app in their web browser, even though they're disconnected. Then it's
> available on the intranet, no learning curve.
>
> Problem is, now I'm faced with a couple thousand new IIS web servers
> (whether they like to admit it or not). Worse off, people are going to
take
> these home and plug them into God knows what network. I'm starting to make
> list of things I want installed, disabled, etc, on these laptops. I have
> some questions about some of the things on my list:
>
> 1) Configure the web site to only be acessible from 127.0.0.1 Can this
> address be spoofed on a w2k machine?
>
> 2) Install a personal Firewall, block everything incoming. Will this
> interfere with requests to the Loopback interface?
>
> Does anyone know of any products that will run asp pages sans IIS/PWS? I
> know I have to point the browser "someplace." I'm wondering if there's a
> creative solution that doesn't require my workstations listening for http
> requests at all.
>
> Thanks in advance,
> -dazed
>
>
>
>
>
>
> _______________________________________________________
> http://inbox.excite.com
>
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]