hi, and thanks. > What you ask is not dumb at all, it sounds perfectly logical. It > sounds to me like you're looking at creating a mash-up of different > applications into a single application. Sort of, the key here is hierarchic mashing up, so one app wants to include a gui-component of the other.
> This is, however, something that requires web services through SOAP or > XML-RPC (or even PHP-RPC for that matter). You would be creating web > services that provide the data in the several different (symfony) > applications, and combining that data in your central application. > Even when using AJAX, this would probably save you some processing > time and bandwidth. The business logic layer and everithing behind that (persistence, interopaerability) is designed just like that. My problem is the (posibbly presumed) conflict between MVC's single controller, and the fact that those included components have their own internal operation. We have many of these planned, for example the date-time picker component, that will provide information on the current users schedule during date selection, but in the end all it does is provides the selected date for the embedding app. > > The only thing I am wondering... which browsers these days do not > support AJAX anymore? I understand the wish to have a fallback system, > just wondering for what kind of system you want this fallback ;) this is for e-government purposes in Eastern europe, so excluding poor people with obsolete infrastucture is not an option, even a no js please checkbox is planned, and we just want to write everything once:) thanks again: s85 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
