Re: Handling Default Document without that Default Document existing

You can also set up a wildcard handler (*) and that will route to Web Connection properly, but... and it's a big but... when you do that you'll lose any capability to auto-route.

Basically what you'd need to do is this:

In yourServer::Process():

• Handle the OTHERWISE clause and provide your own logic to route to a Process class
  
• Create a custom wwProcess class that has custom logic to route your requests to the right method
  

I guess I should look into this some more and see if we can come up with a generic mechanism to make this work, but it's tricky. Basically you'd need some sort of 'route table' to tell Web Connection which Process Class it should map to. So we'd have to have some custom routing mechanism similar to the way in ASP.NET MVC which auto-routes.

When I get some spare cycles I can look into that, but I know some folks have done this before with custom logic in their applications.

+++ Rick ---

Now, I understand the basics of why that subdirectory has to exist and why that file has to exist but my question is, can this be modified easily? If so we could more easily build an MVC type routing structure for Web Connect that would also be cleaner.

~Brett