I don't feel there is enough information to really say if this would
work, however the first thing to come to mind as far as issues would
be cookies / authentication for both domains would need to be handled.
Maybe doing a central "Dashboard" that runs off a single domains and
then do a API type interface to talk with the systems? Just my 2 cents
On Jan 11, 11:22 pm, Alec Taylor <alec.tayl...@gmail.com> wrote:
> What are your thoughts on completely decoupled development?
>
> I have gotten a colleague of mine to work on one whole facet of the
> system, whilst I work on the other. In essence, these are two
> completely separate systems, on two separate domains.
>
> The plan is to link the two in a signup wizard and display a dashboard
> with certain elements of each View.
>
> Given the limited information I have given you, would you recommend
> this method of development? - Do you have recommendation on how we
> would link everything to a View dashboard?
>
> Thanks for all suggestions,
>
> Alec Taylor
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
