Shared Calendar?

Anon

I'm working on a calendar site that I'd like to make searchable (and returnable) to external domains (like a .net service I guess).

Here's the model: master site (mine) hosts a MySQL db, php4.x, etc. This site stores "show" data for venues. External sites can sign-up and allow their visitors to 'post' to my master db (I'm transparent on their site; the visitors think they're just posting to 'joe-client.com' site).
Next, the 'joe-client.com' should be able to allow visitors to search from the client website, returning results from my site.

I'm so-far planning on doing this using a framed-based layout (1px frame, so the visitors think they're still on 'joe-user.com'), but that sucks. I'd rather use XML in/out or something.

Any ideas?

Chad

toma42

Sounds something like jambase.com. Use wddx if you want a quick xml solution.

mike_y

Why not have your users upload a custom header and footer?

Anon

I'm trying to keep as 'transparent' an impression as possible.

Besides, a couple of the participating domains use huuuuge headers and footers, and that just gets ugly (I have done that, however, for a couple select 'premium' domains).

Once I get a filesystem in order where clients can create their own accounts, then I would imagine custom header/footers wouldn't be too much of a pain, I just don't like the whole 'bulletin-board' look/feel of that method.

I think the XML solution would work a little better...just gotta figure it out.

Thanks all.

amcgrath

Why do you think XML solution will work better? I mean, your basically asking for a bloated "Events" listing and display script... they're a dime a dozen. As for the 1-pixel frame idea.... howzabout set up dns for calendar.their-domain.com point to your IP? Then, you can a couple things (namely checking the $HTTP_HOST) to format the page exaclty like there pages.....

Anon

I think the XML solution would work better because it would allow me to simplify the new client registration process, while putting the smallest footprint on their server (most times a virtual hosted, or even free account).

From what I've read of the WDDX solution, the clients servers could use CFM,ASP,PHP,Perl or even JavaScript.

Hell, if a client is using a squatty server, then they could have a js interface that just displays the values, while still allowing them to pass form data (queries) back and forth.

The interactivity level is what's keeping me looking at XML and WDDX.

The only problem I've been faced with so-far is I'm comfortable w/ PHP, but MY vhost doesn't have WDDX compiled (what luck).