pcplantdb

[John Schinnerer <john@eco-living.net>]

Aloha,

With your clarifications below...

> The server should/will implement any kind of search that clients and
> users feel they need.  This is definitely a server element because it
> requires structural knowledge of the database.
>
> There will be methods for free text as well as individual elements
> such as height.  Perhaps in the future we can develop a free text
> search grammar that allows uses a lot of control without having to use
> long forms that list all the various elements.

> More or less exactly.  Markup/format is the clients job whether it's
> html/xml/text or what have you.  It's possible to add an xml
> middleware layer on top of the server to support clients that can't or
> don't want to use xml-rpc.  Keeping it seperated from the server would
> be my preference.

...I think I grok what you're doing well enough to say it sounds good 
and modular and go for it.

> The way I think about it is that you are just importing a package over
> http.  Crazy and cool.  Not only that but you can write the server in
> one language and use the methods in any other language that supports
> xml-rpc!

Yeah, pretty nifty.  Any 'gotchas' that you're aware of?

For example, when you say "importing a package over http" I assume you 
don't mean actually transferring the package modules (the files)...right?

cheers,
John S.

--

John Schinnerer - MA, Whole Systems Design
------------------------------------------
- Eco-Living -
Whole Systems Design Services
People - Place - Learning - Integration
john@eco-living.net
http://eco-living.net