[m-rev.] for review: deep profiler redesign

[Michael Day]

> - The only implementation I know of is in Perl. Integrating that with Mercury
>   code probably won't be easy. Integrating with C code would be a lot easier.
>   Anyone know of a C FastCGI library?

www.fastcgi.com has a C library that can be used from Mercury.

> - It assumes that a given service needs only one server. The natural design
>   for mdprof wants one server per profiling data file, which is significantly
>   different. One could of course build one server for all files, but then
>   you would have to solve the problem of discarding the state of one data file
>   that hasn't been accessed in a long time while keeping the state of other,
>   recently accessed data files. Not conceptually difficult, but annoying.

The FastCGI library allows you to choose one or many servers; however I
don't know exactly how flexible the "many servers" case is. Presumably you
would need to dispatch requests to the appropriate server based on the URL
sent by the client, and I'm not sure if it can do that.

Michael

--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------