[Seaside] Internal/external order tracking system
webmail at pielka.de
Sat Dec 18 11:05:16 UTC 2010
you could run the whole scenario with just one Seaside image if the data volume is not too high.
There are several persistency options described in the seaside book. Personally I prefer to hold the data in the image as regular objects.
This makes developing the application pretty straight forward.
Then you build two web applications with Seaside:
1. One that only can be used by external users to check the status of their orders; you could generate a dedicated Url for each single order that directly leads to the corresponding record/object instance in your Seaside image
2. A second application that requires logon. This is used by the internal users to maintain the order status.
Maybe your order execution system even provides a webservice or other API to import the current order status automatically into your Seaside image.
Am 18.12.2010 um 04:46 schrieb Sean P. DeNigris:
> I want to rewrite a php order tracking system in Seaside.
> Previously, it:
> 1. exported the mysql records from an intranet
> 2. uploaded them to a shared host
> 3. the shared host ran a cron job to import them
> 4. there was a read-only web interface on the shared host for customers to
> check their order status
> I want to make it as simple as possible - I'd love to get rid of the db.
> What's the best way to securely provide read access to external customers
> (only their orders) and read/write to all orders for employees internally?
> I thought about putting it all on VPS, but what happens if the server goes
> down? It would not work for the employees to be locked out for even a few
> View this message in context: http://forum.world.st/Internal-external-order-tracking-system-tp3093410p3093410.html
> Sent from the Seaside General mailing list archive at Nabble.com.
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside