On Sun, 14 Apr 2002 07:29:12 +0530
Ma Siva Kumar <ma_sivakumar@yahoo.com> wrote:
> Fortunately, this particular situation involves simpler relations. It is more
> like this.
>
> Buying companies place orders to their supplier companies. Supplier companies
> maintain the status of orders in the system. Buyer companies can login and
> get information about the order status.
>
> Thus, most of the update of information comes from the internal working of
> supplier companies and the relationship is strictly one to one (what one
> buyer buys from a supplier does not affect any one else in the system).
>
> If everyone uses the central server to update the transactions that is ideal.
> However, atleast in the initial stages, supplier companies may like to
> conduct their day to day operations on the local server (due to connection
> speeds, costs etc) and update the transactions to the central server several
> times a day.
>
> The information flow from the buyer is in the form of new orders, approval of
> samples, payment information etc.
>
> Hope now it is clearer. Even though there will be hundreds of companies in
> the system, each one will have a strictly one to one relationship with
> others.
>
> What is the best possible way to do this using Postgres and PHP?
>
> Best regards,
>
>
> Siva,
> Chennai, Tamil Nadu.
>
<SNIP>
You might want to consider an email based system.
Your system will send email (which can be done via dial-up POP).
Send formated messages back and forth (something like EDI) using
maybe XML or a custom format.
I've done this before for customers who are paranoid about being on the
internet all of the time. Its not hard.
While this is not really much help for PHP (as it web based), it is
just an idea.
GB
