[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Another Glimpse Question (never mind)
- To: Golda Velez <gvelez@tucson.com>
- Subject: Re: Another Glimpse Question (never mind)
- From: Bruce Alexander <balexand@webanswers.com>
- Date: Tue, 17 Aug 1999 12:14:25 -0700
- Organization: WebAnswers, LLC
- References: <37B3402A.AA351C64@webanswers.com> <3.0.2.32.19990817010748.0339d184@tucson.com> <3.0.2.32.19990817104817.02f0d7e8@tucson.com>
- Reply-To: balexand@webanswers.com
I'll look into the way Apache handles shared objects. Maybe I'll set it up to be
straight SO-type logic and put a blurb in there about SSJS interfaces under
Netscape... have to see. It's really quite a mess to link SOs to SSJS apps; but
once you do it you just clone clone clone. There's so many ways to do these
"servlet" apps though that most people will just want to splice out the logic and
ditch the function architecture.
It is real fast, and I'm quite happy with it in general. The big thing for us on
why we want to use glimpseserver vs glimpse/webglimpse is the issue about loading
the index and the code with each call when you run something as CGI. Some of that
can be helped by buffering the indexes and object code into virtual; but you still
have scaling problems if bunches of users are whacking away at once. Anyway, we
like the server model. Not to say I don't love CGI (because I do) but not for
this type of thing.
Anyway, I'll be in touch soonish. I've got everyone giddy with anticipation and
now I need to flesh out the prototype for the test.
Golda Velez wrote:
> Great, sounds good! My only request would be to keep the instructions as
> general as possible, as we have a large install base that might be
> interested in other combinations, like Linux/Apache. Do you think it would
> work with other web servers, or would people have to figure out their own
> ways of interfacing? Apache 1.3 allows loading of shared objects, see
> http://www.apache.org/docs/mod/mod_so.html
>
> It sounds like this way would be much faster than calling webglimpse as a
> CGI script, though some of the result handling stuff would need to be
> re-written. Anyway, I'm sure people will find it useful!
>
> --G
>
> At 08:10 AM 8/17/99 -0700, you wrote:
> >Golda,
> >
> >Thanks for the response, I figured you were probably away having fun
> somewhere
> >so I wasn't in so much of a hurry.
> >
> >I'll have to wait to give you a firm response until I can confer with my boss
> >-- which may take to the end of the week as he's about to head up to the
> >Sierras. However, I'd certainly be willing to give up our glimpseserver
> >interface code with documentation for a 50% discount on the $2000 site
> license
> >for glimpse/glimpseserver.
> >
> >Here's some info on what you would get for your discount (I don't want to
> >oversell it to you). The interface code is written in C and compiled as a
> >Solaris Shared Object. It is then loaded into Netscape Enterprise Server Pro
> >(or any other server capable of using .so libraries) and called as a function
> >by server apps (in this case SSJS). The purpose of the interface is just to
> >act as a conduit to the glimpseserver. The interpretation and
> presentation of
> >the results are handled by the caller. What you will receive is the shared
> >object function source code in Netscape format including function- and
> >line-level documentation. I will include the compile instructions for
> >Solaris. To convert this to some other format (including CGI) the code
> can be
> >included in other parameter format functions. I've used this TCP/IP logic in
> >different remote invocation applications on foreign servers, so I know
> that it
> >works as CGI (but I haven't set up a foreign glimpseserver interface as cgi
> >yet... hmmmmmmmm.).
> >
> >As soon as I have more info from my boss I'll get back to you with a firm
> >answer. That should be by the end of the week.
> >
> >
> >
> >
> >
> >
> >
> >
> >Golda Velez wrote:
> >
> >> Sorry for the delay! I was on vacation last week.
> >>
> >> We don't actually have a separate license agreement for glimpse, we just
> >> package them together. But, I think we could give you some discount if you
> >> only need glimpse. How about 25% discount from our posted prices - or 50%,
> >> if you can give me a nice package with your interface code and some docs
> >> ;-) Or, let me know what you think is fair.
> >>
> >> --G
> >>
> >> At 02:48 PM 8/13/99 -0700, you wrote:
> >> >Never mind, I figured it out. Interesting protocol... I can now interface
> >> >directly with glimpseserver from a shared object in a thread safe
> >> >environment. -- I'd still like to know what the licensing agreement would
> >> >be for just glimpse/glimpseserver without webglimpse.
> >> >
> >> >Thanks.
> >> >
> >> >Bruce Alexander wrote:
> >> >
> >> >> I'm interested in experimenting with a direct program interface to
> >> >> glimpseserver from a shared object interface under Solaris.
> >> >>
> >> >> What input protocol is the glimpseserver expecting? Is there a snippet
> >> >> of code I can look at that explains?
> >> >>
> >> >> Thanks!
> >> >
> >> >Attachment Converted: "c:\eudora\attach\balexand2.vcf"
> >> >
> >> ------------------------------------------------------------
> >> Golda Velez gvelez@tucson.com 520-620-6878
> >> Internet Workshop http://tucson.com
> >> Webglimpse Search Software http://webglimpse.net
> >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >> Help organize the world - index your own corner of the web
> >
> >Attachment Converted: "c:\eudora\attach\balexand3.vcf"
> >
> ------------------------------------------------------------
> Golda Velez gvelez@tucson.com 520-620-6878
> Internet Workshop http://tucson.com
> Webglimpse Search Software http://webglimpse.net
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Help organize the world - index your own corner of the web
Attachment Converted: "c:\eudora\attach\balexand4.vcf"