Macrobyte Resources Conversant Developer Central
Internet groupware development platform
RE: adrObjectToServe not defined




 
Subject RE: adrObjectToServe not defined
Posted 5/31/2002; 3:29 PM by Seth Dillingham
Last Modified 5/31/2002; 3:29 PM by Seth Dillingham
In Response To RE: adrObjectToServe not defined (#294)
Label None. Read 1057
<Previous Next> Thread: Edit Reply

On 5/31/02, John VanDyk said:


>>The smart responder looks for a match in ConversantData.hosts, so that
>>you can have one (or more) hosts which are served by Conversant (a host
>>can be an ip address, a real host name, or a combination of a either of
>>those two with a specific port number like 127.0.0.1:81).
>
>I think I see. I chose the "smart" responder but what I was thinking 
>was that I could serve, say, http://127.0.0.1/myManilaSite and 
>http://127.0.0.1/myZone/myID/ and have Conversant only respond for 
>the second one.

We didn't go with that approach because MainResponder already allows you to do that, via a siteTree in config.mainresponder.domains (I can help you set that up if you want). We could have duplicated that feature in our responder, but it would have been a mostly wasted effort since people who need to run Manila already need to run MainResponder also.

However, you've brought up an interesting point. Did you know you can shorten your Conversant URL's considerably? You can set it up to reach your sites at any of these URL's:

http://host/zone_name/site_name/

http://host/zone_name/

http://host/

Instructions and an explanation are going into the docs, but if you want a quick overview, just ask.

Seth

<Previous Next> Thread: Edit Reply
ENCLOSURES

None.
REPLIES

None.


 
© 2002 Macrobyte Resources. All rights reserved.