Unable to Have Multiple Users on Any Same Step

[rich-armstrong]

We tried having multiple users working through the same processes today on the Prospector App. When working on each respective process it would be expected that the user is able to see different jobs represented if multiple processes for the same step are being completed on different machines. For example, if two people are trying to knock out the "Contact Broker" process it will only pull up a single phone number/ property list combo. Prospector needs the ability to differentiate between different users working on the same task.

-Chris/Richard

[jahio]

Hey guys,

This is not a bug. The application was never built to parallelize multiple users and divvy up workload like you're asking. Any user who performs a simple GET request on a resource (as this is how any standard web application is going to work) will just get the next one in line, regardless of who's doing what.

That said, this isn't impossible but I'm not sure I feel comfortable implementing this in the existing codebase. This is because the existing code is so far departed from what is actually needed in terms of the business use case that I've had to implement some truly ugly hacks to get it limping along. I'm worried that introducing domain logic like this could hurt more than it helps (introduce multiple unknown/unforeseen bugs). It's also not necessarily an easy/cheap feature to implement.

I'd suggest an internal discussion around this before you ask me to implement this feature. My suggestion would be to do your best to work around it. Might be painful, but it's less painful than more bugs that we don't find until later because I'm in the process of adding more complexity to an already tangled rat's nest of hacktastic logic.

[realmassiveCEO]

This is not a necessary feature for launch. Please set aside for later discussion.

On Wednesday, January 29, 2014, J. Austin Hughey notifications@github.com wrote:

Hey guys,

This is not a bug. The application was never built to parallelize multiple users and divvy up workload like you're asking. Any user who performs a simple GET request on a resource (as this is how any standard web application is going to work) will just get the next one in line, regardless of who's doing what.

That said, this isn't impossible but I'm not sure I feel comfortable implementing this in the existing codebase. This is because the existing code is so far departed from what is actually needed in terms of the business use case that I've had to implement some truly ugly hacks to get it limping along. I'm worried that introducing domain logic like this could hurt more than it helps (introduce multiple unknown/unforeseen bugs). It's also not necessarily an easy/cheap feature to implement.

I'd suggest an internal discussion around this before you ask me to implement this feature. My suggestion would be to do your best to work around it. Might be painful, but it's less painful than more bugs that we don't find until later because I'm in the process of adding more complexity to an already tangled rat's nest of hacktastic logic.

Reply to this email directly or view it on GitHubhttps://github.com/realmassive/prospector/issues/25#issuecomment-33565157 .

---

Joshua McClure Founder & CEO www.RealMassive.com c: 512.630.1433 t: @realmassive

• Commercial Real Estate in Real-Time*

----- This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.