从驱动程序许可证中捕获名称 // PCI 读卡器
我有一个 iMag PCI 读卡器和一个与之配套的 SDK。话虽如此，我是一个相当新手的 iOS 开发人员，所以 SDK 对我来说并不完全清楚。
我的项目目标是这样的； PCI 读卡器连接到 iPad - 该应用程序有多个用于数据输入的文本字段，包括名称字段。为了加快登录和注销的过程，以及增加安全性的感觉（我在数据中心工作），我希望让读卡器刷政府颁发的 ID（州许可证），然后存储 - 只是名字 -在文本字段中。这确保了我们数据库中的信息准确无误，并且“您就是您所说的那个人”。自动时间戳也是一个优点。
之后，用户手动输入其他文本字段，例如“访问原因”。登录时间在提交到数据库时被存储。要注销，用户只需在应用程序内选择不同的视图，刷一下 ID，然后就可以退出。
警告 - 内部同名的人同时可能会导致问题，但我真的没有看到这种情况发生:-)
- 过去是否有人完成过类似的项目？总的来说，该应用程序应该有大约 4 个视图，以及简单的图片/文本/和一些文本输入表单。
我想弄清楚的是，我存储在文本字段中输入的数据，然后将其卸载到数据库，然后注销的方法是否会对我的应用程序从中提取用户名称的方式产生直接影响许可证。或者说从开发角度来说是完全独立的，可以独立处理？
任何帮助或建议将不胜感激。我做了一些论坛搜索，PCI读卡器似乎是一个相当分散的市场，所以我不知道是否有很多人会熟悉iMag，或者我随它收到的SDK。
谢谢，
查理
I have an iMag PCI card reader and an SDK that goes along with it. Having said that, I'm a pretty novice iOS developer, so the SDK isnt completely clear to me.
My project goal is this; PCI card reader is connected to an iPad - The app has multiple text fields for data entry, including a Name field. To speed the process of Login and Logout, along with the feeling of increased security (I work at a data center), I was hoping to make the card reader swipe a government issued ID (state license), and store -just the name- in a text field. This assures that that the information in our database is accurate, and "you are who you say you are". An automated timestamp is also a plus.
Following that, the user then manually enters other text fields, such as "Reason for Visit". Time time of login is stored upon submission into a database. To Logout, the user simply selects a different View inside the app, swipes their ID, and can walk out.
Caveats- persons with the exact same name on premise concurrently could cause a problem, but i really dont see that happening :-)
-- Has anyone completed a project similar to this in the past? Altogether, the App should have about 4 views, and simple pictures/text/ and a handful of text entry forms.
Something I'm trying to figure out is wether my method of storing the data entered in the text fields, then offloading that to a database, and then also logging out will have a direct impact on how my app pulls the Name of the user from a license. Or are those completely independent from a development perspective, and can be handled independently?
Any help or advice would be greatly appreciated. I did some forum searching and the PCI card readers seem to be a pretty fragmented market, so I don't know if many people will be familiar with the iMag, or the SDK i have received along with it.
Thanks,
Charlie
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
无论您是通过用户键入数据还是通过刷卡获取数据，对于最终将其存储在数据库中的方式都没有什么影响。我们这里有一个类似的流程：我们使用条形码扫描仪，因此用户可以使用条形码扫描产品 ID，或者如果商品没有条形码标签或已损坏且无法扫描或其他任何情况，他们可以将其键入。我们用产品 ID 填充表单上的字段，然后程序就不知道或关心它来自哪里。
“同时在场的同名人员可能会导致问题，但我真的没有看到这种情况发生”我会非常谨慎，只是希望这种情况永远不会发生。如果/当它发生时会发生什么？我见过很多系统，其中有人说：“哦，这种情况发生的概率是一百万比一，我们只是不会担心它。”然后在系统部署的第一天，就发生了两次。 “通常应该工作”的系统是非常可怕的。我不知道您一次可能有多少客户。您打算在两次访问之间保存数据吗？是只有两个同名顾客同时在店里才会有问题，还是如果两个曾经是顾客的人同名才会有问题？但即使他们必须同时在商店里制造麻烦，这种情况也可能发生。使用驾驶执照来验证客户的姓名可能是个好主意，但不要将其用作客户的标识符：为他们提供一些唯一的 ID。
其他杂念：
“要注销，用户只需在应用程序内选择不同的视图，刷一下 ID，然后就可以退出。”为什么用户需要再次滑动才能退出？其他人是否有可能在未经本人同意的情况下将其注销？但要发生这种情况，用户必须在登录时离开终端。如果其他人可以走上来并开始使用该人的 ID 下的系统，那么他们将其注销的可能性应该是最小的。安全问题。如果有人离开商店（或其他任何地方）而没有再次刷卡怎么办？他们会永远保持登录状态吗？我认为，如果有人没有注销就离开，您希望让某人可以轻松地单击按钮并注销他们。
我不知道你的应用程序。您是否可以拥有没有驾驶执照或拥有其他州驾驶执照的用户？我不知道驾驶执照磁条上存储的数据是否有任何标准，或者是否所有州都有磁条。
Whether you get data by the user keying it in or by picking it up from a card swipe should make no difference to how you ultimately store it on a database. We have a similar process here: we use barcode scanners, so the user can scan the product id with the barcode, or if an item has no barcode label or it's damaged and won't scan or whatever, they can key it in. Either way we populate a field on the form with the product id, and from there on the program doesn't know or care where it came from.
"persons with the exact same name on premise concurrently could cause a problem, but i really dont see that happening" I'd be very cautious about just hoping this will never happen. What happens if/when it does? I've seen plenty of systems where someone said, "Oh, the probability of that ever happening is a million to one, we just won't worry about it." Then the first day the system is deployed it happens twice. Systems that "ought to usually work" are very scary. I don't know how many customers you might have at one time. Do you plan to save data between visits? Is there only a problem if two customers with the same name are in the store at the same time, or is there a problem if two people who were EVER customers have the same name? But even if they both have to be in the store at the same time to cause trouble, it could happen. Using a drivers license to validate the customer's name might be a good idea, but don't use that as the identifier of the customer: give them some unique id.
Other stray thoughts:
"To Logout, the user simply selects a different View inside the app, swipes their ID, and can walk out." Why does the user need to swipe again to log out? Is there a potential that someone else could log the person out without their consent? But for that to happen, the user would have to walk away from the terminal while logged in. If someone else can walk up and start using the system under that person's id, the possibility that they will log them out should be the least of your security concerns. And what if someone leaves the store (or whatever this is) without swiping again? Do they stay logged in forever? I would think that if someone walks away without logging out, you WANT to make it easy for someone to just click a button and log them out.
I don't know your app. Could you have users who don't have a drivers license, or who have a license from a different state? I don't know if there's any sort of standard about data stored on the mag strip on drivers licenses, or if all states have mag strips.