using internal iPad camera

[nbcl-kkgreene]

Would want to be able to use the front and back camera. Would you be able to use another iPad's camera?

[nbcl-rossm]

This would involve writing an iOS based WSBD service. Not beyond the realm of the possible, but not trivial.

Sent from BlackBerry

----- Original Message -----
From: nbcl-kkgreene [email protected]
To: Micheals, Ross J.
Sent: Thu Jul 05 18:51:31 2012
Subject: [wsabi2] wishlist: using internal iPad camera (#77)

Would want to be able to use the front and back camera. Would you be able to use another iPad's camera?

---

Reply to this email directly or view it on GitHub:
https://github.com/nbcl-kayee/wsabi2/issues/77

[nbcl-kkgreene]

On Jul 5, 2012, at 7:41 PM, nbcl-rossm wrote:

This would involve writing an iOS based WSBD service.

Unless you "fake it" and just get direct access to the iPad camera, which is what I believe one version of WSABI 1.0 did. But as far as exercising the standard, that's probably not the best way to go :)

Not beyond the realm of the possible, but not trivial.

Based on our meeting yesterday, it seems there might be a pretty significant issue with this that I didn't realize before: iOS doesn't really run things in the background on the iPad, so without really fiddling with the innards, having the service running and using the wsabi app simultaneously on the same iPad could be a problem. However, is there a reason that one iPad couldn't run the service and a second iPad do the capturing? In fact, that would make "wsabi to go" even easier than with the laptop (provided the fingerprint sensors are self-powered and don't need the laptop's USB port).

[nbcl-rossm]

This would involve writing an iOS based WSBD service.

Unless you "fake it" and just get direct access to the iPad camera, which is what I believe one version of WSABI 1.0 did. But as far as >exercising the standard, that's probably not the best way to go :)

Exactly.

Not beyond the realm of the possible, but not trivial.

Based on our meeting yesterday, it seems there might be a pretty significant issue with this that I didn't realize before: iOS doesn't >really run things in the background on the iPad, so without really fiddling with the innards, having the service running and using the >wsabi app simultaneously on the same iPad could be a problem. However, is there a reason that one iPad couldn't run the service >and a second iPad do the capturing? In fact, that would make "wsabi to go" even easier than with the laptop (provided the ?>fingerprint sensors are self-powered and don't need the laptop's USB port).

Yes, the service would have to be a either a background service, or dedicated/sovereign preventing other things from running. Greg F may be able to help answer if a background HTTP server is even possible.

---

Reply to this email directly or view it on GitHub:
https://github.com/nbcl-kayee/wsabi2/issues/77#issuecomment-6804270

[nbcl-kkgreene]

On Jul 6, 2012, at 9:02 AM, nbcl-rossm wrote:

This would involve writing an iOS based WSBD service.

Unless you "fake it" and just get direct access to the iPad camera, which is what I believe one version of WSABI 1.0 did. But as far as >exercising the standard, that's probably not the best way to go :)

Exactly.

Not beyond the realm of the possible, but not trivial.

Based on our meeting yesterday, it seems there might be a pretty significant issue with this that I didn't realize before: iOS doesn't >really run things in the background on the iPad, so without really fiddling with the innards, having the service running and using the >wsabi app simultaneously on the same iPad could be a problem. However, is there a reason that one iPad couldn't run the service >and a second iPad do the capturing? In fact, that would make "wsabi to go" even easier than with the laptop (provided the ?>fingerprint sensors are self-powered and don't need the laptop's USB port).

Yes, the service would have to be a either a background service, or dedicated/sovereign preventing other things from running. Greg F may be able to help answer if a background HTTP server is even possible.

I think the answer is only with jail breaking, but I could be wrong.

[nbcl-rossm]

It may be possible to host wsabi and an http server in the same process.

-----Original Message-----
From: nbcl-kkgreene [mailto:[email protected]]
Sent: Friday, July 06, 2012 9:17 AM
To: Micheals, Ross J.
Subject: Re: [wsabi2] wishlist: using internal iPad camera (#77)

On Jul 6, 2012, at 9:02 AM, nbcl-rossm wrote:

This would involve writing an iOS based WSBD service.

Unless you "fake it" and just get direct access to the iPad camera, which is what I believe one version of WSABI 1.0 did. But as far as >exercising the standard, that's probably not the best way to go :)

Exactly.

Not beyond the realm of the possible, but not trivial.

Based on our meeting yesterday, it seems there might be a pretty significant issue with this that I didn't realize before: iOS doesn't >really run things in the background on the iPad, so without really fiddling with the innards, having the service running and using the >wsabi app simultaneously on the same iPad could be a problem. However, is there a reason that one iPad couldn't run the service >and a second iPad do the capturing? In fact, that would make "wsabi to go" even easier than with the laptop (provided the ?>fingerprint sensors are self-powered and don't need the laptop's USB port).

Yes, the service would have to be a either a background service, or dedicated/sovereign preventing other things from running. Greg F may be able to help answer if a background HTTP server is even possible.

I think the answer is only with jail breaking, but I could be wrong.

---

Reply to this email directly or view it on GitHub:
https://github.com/nbcl-kayee/wsabi2/issues/77#issuecomment-6804649

[gfiumara]

It may be possible to host wsabi and an http server in the same process.

This is doable, though I'd start small with a dedicated app that acts as the WS-BD service. You'd run this on a second iPad on the network. The service would accept and reply to WS-BD messages while the app is in the foreground and could receive a push notification while in the background to say someone wants access.

As far as a long-running background task, this is not possible without jail-breaking, and even then I'm not sure. Apps are only "backgrounded" for a few seconds, enough time to do a small, finite-length task. After that, the process is suspended without notification. The OS can also kill the app without notification at any time due to low memory conditions on the device.

[nbcl-rossm]

PhoneGap source code may be a place to look as well. Starting it as a dedicated app is a good idea.

-----Original Message-----
From: Greg Fiumara [mailto:[email protected]]
Sent: Tuesday, July 10, 2012 11:42 AM
To: Micheals, Ross J.
Subject: Re: [wsabi2] wishlist: using internal iPad camera (#77)

It may be possible to host wsabi and an http server in the same process.

This is doable, though I'd start small with a dedicated app that acts as the WS-BD service. You'd run this on a second iPad on the network. The service would accept and reply to WS-BD messages while the app is in the foreground and could receive a push notification while in the background to say someone wants access.

As far as a long-running background task, this is not possible without jail-breaking, and even then I'm not sure. Apps are only "backgrounded" for a few seconds, enough time to do a small, finite-length task. After that, the process is suspended without notification. The OS can also kill the app without notification at any time due to low memory conditions on the device.

---

Reply to this email directly or view it on GitHub:
https://github.com/nbcl-kayee/wsabi2/issues/77#issuecomment-6879257