That would've been ideal. However I asked our webhost and they want 2100+ Danish Marks (Dotserv - tight "#"#"#!" - needless to say it isn't going to happen) to configure cURL within their PHP, can't do cron jobs either.
They suggest I use wget to do the same thing, however the only way I can think of to do that is display the submissions on a page and and somehow parse that into SQL to insert it. Any ideas on how I can go about that? Cheers, Steve Jackson Web Developer Viola Systems Ltd. http://www.violasystems.com [EMAIL PROTECTED] Mobile +358 50 343 5159 > -----Original Message----- > From: Ernest E Vogelsinger [mailto:[EMAIL PROTECTED] > Sent: 27. maaliskuuta 2003 10:14 > To: Steve Jackson > Cc: PHP General; 'Christopher E. Welton' > Subject: RE: [PHP] Passing data between the web to an Intranet > > > Here's some ideas how I'd go for something like that. I'd > have some PHP on the externally hosted website, and some PHP > on the Intranet/CRM-DB server. > > At 08:39 27.03.2003, Steve Jackson said: > --------------------[snip]-------------------- > >gathering tool. Basically what I'll need to set-up is some sort of > >system which: > >1) Validates user input from the web (php) > > Should be done on the external website box. > > >2) Sends the information to the external website DB for > future customer > >login authentication (php> mysql>update/insert) > > Same thing here - PHP on the external box. > > >3) Sends the information to our internal website DB > (Intranet server) > >(email or replication?) > > A PHP form residing on the internal box to receive POSTed > data from the external box. The external box would use cURL > to post aony content that needs to go internal. > > >4) Flags our people here when a new prospect arrives (php>email) > >5) Full front end system for the prospect details etc (Intranet > >server). > >(php/mysql) > > Both internally, PHP intranet style. > > Using this approach you have full control over what goes into > the internal DB; much better for this task IMHO than > replicating a complete DB. > > Of course you need to make sure that only the external webbox > can post to the Intranet server, the level of authorization > depends on your security considerations and the network layout. > > If the Intranet host only has a private IP (192.168.*, or > 10.*) but can be reached by the external box via secondary > interface this aint really an issue since it can't be reached > from the outside. If the Intranet box _could_ be reached from > the outside I'd recommend to run the receiving form on an SSL > interface, the external box using a client certificate to > authenticate itself. AFAIK this can be done with cURL. > > HTH, > > -- > >O Ernest E. Vogelsinger > (\) ICQ #13394035 > ^ http://www.vogelsinger.at/ > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
