A few more details would make it easier to provide help. There are a number of alternatives, but the details will vary based on, among other things, what form your "database" takes.
Is it a SQL database on a web-accessible machine? If so, it is (in theory) no different than if the database was at the "other site" on a machine dedicated to the database server -- a common setup.
You could provide your data in any number of XML formats including RSS.
If you provide specifics, you'll get some very specific suggestions here. | [reply] |
Someone on either end of your connection is going to have to parse the data into an HTML page that blends into their site. The suggestions above are ideal if they can parse XML or comma delimited data.
Another way, if you are dealing with non-CGI people, is to get a template of their page from them and set up a cgi script that takes the parameters they want, then outputs the page formatted for their site. They could use a frameset for seamless integration. The disadvantages are much heavier load on your system and you would have to make changes if the templates changed (unless they left the templates somewhere and your script checked them periodically for updates).
Another option that might be beyond your skills, but very useful to learn and play with would be to set up a socket to listen for specific commands. You could then output pre-formatted HTML, XML or whatever they request and they would not have to do too much or any extra processing. I say VERY specific commands because you do not want to allow raw sql or server or perl into the socket, just a limited range of commands you make available for their needs.
I realize these suggestions are pretty vague, I just wanted to give you some ideas to think about. | [reply] |
have your site accept standard CGI variables and return csv or similar delimited content that can be parsed. they can use LWP and treat it like a flatfile/cursor.
or you could html format it as you like and they can use LWP just to redisplay/frame with their own branding.
| [reply] |
Actualy, it is a text database that displays a list of events, The exact content that I would like displayed on the other sites looks like this:
http://www.fouye.com/fet/cgi-bin/fet.pl?action=qlist
fet.pl is the main script but providing Just the list of events and making it blend with the other persons site would be more than satisfactory
thanks | [reply] |
Looking at your, er, colorful listing, it is going to be difficult to get your sight to blend with anyone else's sight.
Your choices seem to be, a) provide the entire page (i.e., all the HTML), b) provide the content of the listing and let them suck it up (via LWP::Simple, e.g.) and format it themselves.
I suspect that the programming capabilities on the receiving end are varied, and insufficient.
You could just provide the whole page, but via query parms allow for different style sheets to be pulled in. If you want to maintain profile information, you could do all manner page customiziation on your end, such as custom logos, etc.
| [reply] |
strip out all of the formatting and provide it in a simple format, such as (as suggested) XML or csv. If you expect anyone to request your content, you need to make it easy to obtain and manipulate. Your HTML appears to be pretty complex, too; the way you've structured the nested tables for the events is beyond my ken -- perhaps it's just to achieve a certain look & feel, but I'd cringe trying to parse or regex that...
| [reply] |