我的任务是将Rets I集成到基于PHP的网站。我听说Phrets是一个很好的图书馆。该网站位于共享的托管平台(Godaddy)上。我以为我可以构建一个带有一些搜索字段的页面,并进行查询并在第二页上显示结果吗?我读过的其他地方听起来更像是我仍然需要运行一个本地服务器,该服务器复制数据并在本地存储。现在我不确定该怎么办。任何建议或帮助将不胜感激。

有帮助吗?

解决方案

首先...从共享服务器和您可以获取root访问的某个地方。 RET需要访问端口6103,共享服务器将阻止对其的访问。其次,PHP是RET的一个非常好的处理工具。 Vielerets建立在PHP中,这是房地产经纪技术中心建造的重要软件……相同的人创建了RETS标准。

其他提示

我查看了来自Rets开发小组的产品,我保证如果您遵循开发人员概述的指南,您将不了解RET或IDX,因为该站点上使用的术语在大多数级别上都是错误的。我会坚持使用Vielerets或其他产品。

使用Java的RETS IQ是实施而不是Phrets的更好方法

使用RETS IQ Java为RET创建良好的数据供稿拱门,然后在数据库中推动该解决方案更好的解决方案

Actually it will work using PHP on a shared server if:

  • You have a host that allows access to port 6103. As other people have pointed out this is not the norm and definitely not with Godaddy, but there are a few out there.
  • You are covering a market that is not huge.
  • You optimize and optimize again your requests from the RETS server to only pull changes.

So if you have a limited budget (which seems to be common with realtors) you can:

  • Use a shared host (on an accommodating hosting service).
  • You will need to create a local database for displaying your results.
  • Set up a cron job to pull down changes from the RETS server say every 24 hours preferably when the server is likely to not be under load, like at night.
  • Construct a RETS query to only pull listings from the area you care about.
  • Query the server for changes and only pull changed/new listings.
  • Save on bandwidth and server load if your RETS service has an image hosting service, rather than download them to your server.

But you are playing with fire - pulling a lot of records and images takes time and could lead to the hosting account being disabled.

NB: I would not necessarily rely on the change list from the RETS server. I have been burnt before by it giving invalid data.

即使您是Master PHP开发人员,也不要尝试使用PHP与RET一起工作,您也会失败,因为PHP不是RET处理的工具。

就是说。 rets的DefAtto工具是库,它具有与Ruby,Python和我相信C#以及本机C ++实现的兼容SWIG绑定。

最后,在技术上有可能使Web请求从RET查询中删除RET查询,取回结果,然后转换数据以进行演示,但是相对简单的查询很可能会因负载而进行15-30秒以上。遥控器RET服务器。因此,通常最好构建或找到软件来复制MLS的所有或某些活动列表。

许可以下: CC-BY-SA归因
不隶属于 StackOverflow
scroll top