Ross Gardler wrote:
These alternative clients, which
include OSCommerce and the custom PHP scripts you mention, would plugin
in like this:
.--------.
.------. .-----------. .------------. .---------. | HTML |
| | | | | Cocoon | | |-->`--------'
| DB |<--->| Hibernate |--->| Generator |--->| Forrest | .--------.
| | | | | | | |-->| PDF |
`------' `-----------' `------------' `---------' `--------'
| | | .--------.
| `----------------`------->| XML |
| `--------'
| .------------.
`---------->| Client |
`------------'
Sorry, that is incorrect. OSCommerce plugs directly into the DB. I don't
know PHP so I'm not sure if you can make it talk to a hibernate back
end, so your PHP scripts may need to talk directly to the DB as well.
Although it could pull formatted data or raw XML from the Forrest app if
it needs to. This would give us:
.-------------.
| non-Cocoon |
.--------------.---------->| Client |
| | `-------------'
| | /|\
| | '----------------.
| | | .--------.
.------. .-----------. .------------. .---------. | HTML |
| | | | | Cocoon | | |-->`--------'
| DB |<--->| Hibernate |--->| Generator |--->| Forrest | .--------.
| | | | | | | |-->| PDF |
`------' `-----------' `------------' `---------' `--------'
| | .--------.
| `------->| XML |
\|/ `--------'
.------------.
| Cocoon |
| Client |
`------------'
It would be more robust, and most likely faster, to use Cocoon Forms to
create your client apps in the way the above diagram shows. However, I
understand your point about "time to learn Cocoon Forms", that
implementation decision is, of course, your own.
Ross