Peter Szinek
4/28/2008 6:32:00 AM
> PS. 4th question Peter I forgot:
> =95 does it support downloading a file (eg csv file, account =20
> transactions)
>
> On 4/27/08, Greg Hauptmann <greg.hauptmann.ruby@gmail.com> wrote:
>> sounds good, it support:
>> =95 https?
>> =95 cookies?
>> =95 building in some intelligence? (say when the link for step N will
>> change over time but you can write an algorithm for it)
>>
Yes, scRUBYt! supports all these things... In the current =20
implementation WWW::Mechanize is used as the agent, but it doesn't =20
support JavaScript and (more often than not) e-banking sites have =20
some JS... so that's why I suggested the FireWatir based solution.
A browser-agnostic solution doesn't exist (Mechanize is a browser too) =20=
- the nature of the task requires a browser. Call it as you like, but =20=
if something is able to GET/POST requests, store cookies, use https, =20
sessions, .... then it is a browser in my vocabulary.
Besides FireWatir is platform-independent (unlike Watir which is win32 =20=
only).
Cheers,
Peter=